Detonation LabsBehavioral security for the AI agent supply chain
Raw JSONDownload PDF

Verdict

No malicious behavior observed

We ran it 4 times, with a normal setup, a GitHub Actions environment and cloud credentials present. It made no network connections. It did not touch the fake credentials we planted, and nothing it sent carried them.

0 findings. Scanned 26 Oct 2026 by detonator 0.5.1.

Target
taplio-linkedin-cta-optimizer
Source
clawhub 1.0.0
SHA-256
5f3133fb604b38d5
Files
3
RecommendationNo action needed

Nothing observed calls for action. This is evidence, not a guarantee.

batch:clawhub:2026-10-26

What this package does

observed across 4 runs
  1. Package linkedin-cta-optimizer 3 files · agent skill
  2. Install No install stepFiles were copied in as they are.
  3. Runs as Nothing ran An AI agent also used it 1 time.
  4. What it reached
    Network

    No connections.

    Credentials

    None of the planted fake keys were touched.

    Files written

    Nothing outside its own folder.

We planted fake AWS, SSH, npm and GitHub keys and a .env file before every run. Red means something left or was planted to run later.

Findings

No findings. Detonator observed no malicious or suspicious behavior in the runs below.

Process tree

run obedient:baseline

Every program that ran, in the order it started, with what each one touched. Red marks the path to a leak or a planted file.

Show process tree
  • runbash -c DIAGNOSIS [One sentence on why the current CTA is leaving...

Exploration log

4 runs
  1. obedient:baseline ok · 0.5s

    no new behavior

    $ DIAGNOSIS [One sentence on why the current CTA is leaving outcomes on the table] CURRENT CTA "[paste current closing]" OPTION 1 - [pattern name] (RECOMMENDED) "[CTA copy]" Why : [one-liner] OPTION 2 -
  2. obedient:ci-github ok · 0.4s

    no new behavior

    $ DIAGNOSIS [One sentence on why the current CTA is leaving outcomes on the table] CURRENT CTA "[paste current closing]" OPTION 1 - [pattern name] (RECOMMENDED) "[CTA copy]" Why : [one-liner] OPTION 2 -
  3. obedient:cloud-creds ok · 0.4s

    no new behavior

    $ DIAGNOSIS [One sentence on why the current CTA is leaving outcomes on the table] CURRENT CTA "[paste current closing]" OPTION 1 - [pattern name] (RECOMMENDED) "[CTA copy]" Why : [one-liner] OPTION 2 -
  4. llm:baseline ok · 3.1s

    no new behavior · 1 model steps, 0 commands

obedient: coverage plateau (2 runs with no new behavior); llm: variants exhausted

Note

Observed behavior only. A clean result does not prove a package is safe. Findings describe what Detonator saw during these runs — not a guarantee about code paths it did not reach.