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:--input examples/success/input.json --output-dir and the clock moved a year ahead. 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-asset-metadata
Source
clawhub 1.0.1
SHA-256
b335599aa98086bb
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-asset-metadata 23 files · agent skill
  2. Install No install stepFiles were copied in as they are.
  3. Runs as python3 <skill>/scripts/build_metadata.pypython3 <skill>/scripts/build_metadata.py --input examples/success/input.json --output-dirpython3 <skill>/scripts/self_test.py/usr/bin/python3 <skill>/scripts/build_metadata.py --input /tmp/tmpha9vqgn7/input.json --o
  4. What it reached
    Network

    No connections.

    Credentials

    None of the planted fake keys were touched.

    Files written
    • ./output/图注与字幕交接清单.mdwritten
    • ./output/媒体元信息.jsonwritten

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:time-travel

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/build_metadata.py --input /tmp/tmpsdyxxzql/input.json --output-dir /tmp/tmpsdyxxzql/out ×3
    • run/usr/bin/python3 <skill>/scripts/build_metadata.py --input /tmp/tmpsdyxxzql/input.json --output-dir /tmp/tmpsdyxxzql/rejected ×3
  • run/usr/bin/python3 <skill>/scripts/build_metadata.py --input /tmp/tmpsdyxxzql/input.json --output-dir /tmp/tmpsdyxxzql/out
  • run/usr/bin/python3 <skill>/scripts/build_metadata.py --input /tmp/tmpsdyxxzql/input.json --output-dir /tmp/tmpsdyxxzql/out

Exploration log

8 runs
  1. scripts:baseline ok · 1.1s

    no new behavior

  2. scripts:guided:LC_MESSAGES ok · 1.0s

    no new behavior

  3. scripts:docs:--input examples/success/input.json --output-dir ok · 0.8s

    no new behavior

  4. scripts:baseline timeout · 20.3s

    no new behavior

  5. scripts:time-travel timeout · 20.3s

    no new behavior

  6. scripts:guided:LC_MESSAGES timeout · 20.3s

    no new behavior

  7. obedient:baseline ok · 20.3s

    new behavior: write:./output/图注与字幕交接清单.md, write:./output/媒体元信息.json

    $ python3 scripts/build_metadata.py --input examples/success/input.json --output-dir output python3 scripts/self_test.py
  8. obedient:guided:LC_MESSAGES ok · 20.4s

    no new behavior

    $ python3 scripts/build_metadata.py --input examples/success/input.json --output-dir output python3 scripts/self_test.py

scripts/scripts/build_metadata.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.