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

Verdict

No malicious behavior observed

We ran it 8 times, with a normal setup, LC_MESSAGES set, docs:check --input repair.json and a GitHub Actions environment. It made no network connections. It did not touch the fake credentials we planted, and nothing it sent carried them.

0 findings. Scanned 27 Oct 2026 by detonator 0.5.1.

Target
aimegeo-sentiment-repair
Source
clawhub 1.0.1
SHA-256
407aed07c6476830
Files
23
RecommendationNo action needed

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

batch:clawhub:2026-10-27

What this package does

observed across 8 runs
  1. Package aimegeo-sentiment-repair 23 files · agent skill
  2. Install No install stepFiles were copied in as they are.
  3. Runs as python3 <skill>/scripts/repair_bundle.pypython3 <skill>/scripts/repair_bundle.py check --input repair.jsonpython3 <skill>/scripts/self_test.py/usr/bin/python3 <skill>/scripts/repair_bundle.py check --input /tmp/tmpl2yf26rt/ambiguous
  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 scripts:ci-github

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
  • runpython3 <skill>/scripts/self_test.py
    • run/usr/bin/python3 <skill>/scripts/repair_bundle.py check --input /tmp/tmpqrpecksh/ambiguous.json
    • run/usr/bin/python3 /tmp/tmptowo0jc4/standalone/scripts/repair_bundle.py export --input /tmp/tmptowo0jc4/standalone/examples/failure/input.json
  • run/usr/bin/python3 /tmp/tmptowo0jc4/standalone/scripts/repair_bundle.py export --input /tmp/tmptowo0jc4/standalone/examples/success/input.json

Exploration log

8 runs
  1. scripts:baseline ok · 1.1s

    no new behavior

  2. scripts:guided:LC_MESSAGES ok · 1.1s

    no new behavior

  3. scripts:docs:check --input repair.json ok · 1.1s

    no new behavior

  4. scripts:baseline ok · 6.6s

    new behavior: write:./aimegeo-follow-through.md, write:./ambiguous.json, write:./delivery, write:./examples

  5. scripts:guided:LC_MESSAGES ok · 5.5s

    no new behavior

  6. scripts:ci-github ok · 5.1s

    no new behavior

  7. obedient:baseline ok · 7.2s

    no new behavior

    $ python3 scripts/repair_bundle.py check --input repair.json python3 scripts/repair_bundle.py export --input repair.json --output-dir delivery python3 scripts/self_test.py
  8. obedient:guided:LC_MESSAGES ok · 7.5s

    no new behavior

    $ python3 scripts/repair_bundle.py check --input repair.json python3 scripts/repair_bundle.py export --input repair.json --output-dir delivery python3 scripts/self_test.py

scripts/scripts/repair_bundle.py: coverage plateau (2 runs with no new behavior); scripts/scripts/self_test.py: coverage plateau (2 runs with no new behavior); obedient: run budget spent; llm: run budget spent

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.