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, LC_MESSAGES set 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.

2 findings. Scanned 27 Oct 2026 by detonator 0.5.1.

Target
site-traffic-teardown
Source
clawhub 0.1.2
SHA-256
2f1575c226f3503b
Files
5
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 4 runs
  1. Package site-traffic-teardown 5 files · agent skill
  2. Install No install stepFiles were copied in as they are.
  3. Runs as python3 <skill>/scripts/teardown.pyls -lals -la skillcat skill/SKILL.md An AI agent also used it 1 time.
  4. What it reached
    Network

    No connections.

    Credentials
    • ./.envread

    ~/.npmrc read by its own tool (normal)

    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

F01 Low

Loaded the project's .env file

Confidence
Info The package loaded the project's .env file.
Observed in
llm:baseline

Description

The process loaded the project's .env file. Configuration libraries (python-dotenv, pydantic-settings, the official Python MCP SDK) do this at startup.

Impact

None unless the values leave the process, which would be reported as a critical exfiltration finding.

Evidence

./.env (by sed)

Remediation

No action needed. Keep long-lived secrets out of project .env files where possible.

F02 Low

A tool read its own credentials (e.g. gh, aws, ssh)

Confidence
Info A tool opened its own login or config file, such as npm reading ~/.npmrc.
Observed in
llm:baseline

Description

A tool opened its own configuration or login file, such as npm reading ~/.npmrc or gh reading its hosts file.

Impact

None in itself: this is how those tools work. Listed so the report shows every credential access.

Evidence

~/.npmrc (by npm)

Remediation

No action needed.

Process tree

run llm: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.

  • runbash -c cd "$(pwd)" && command -v aisa; echo "exit=$?"; aisa --ve...
    • runsed s/=.*/=<redacted>/ .env
      • secretread ./.env
View full process tree
  • runbash -c cd "$(pwd)" && ls -la && ls -la skill && cat skill/SKILL....
    • runls -la
    • runls -la skill
    • runcat skill/SKILL.md
    • runhead -5
  • runbash -c which aisa && aisa --version && aisa whoami 2>&1 | head -20
    • runwhich aisa
  • runbash -c cd "$(pwd)" && command -v aisa; echo "exit=$?"; aisa --ve...
    • runsed s/=.*/=<redacted>/ .env
      • secretread ./.env
    • runcat README.md
    • runcat package.json
    • runls src
    • runcat .gitignore
  • runbash -c cd "$(pwd)" && ls skill/scripts skill/references && cat s...
    • runls skill/scripts skill/references
    • runcat skill/_meta.json
    • runcat skill/skill-card.md
  • runbash -c cd "$(pwd)" && sed -n '1,80p' skill/scripts/teardown.py; ...
    • runsed -n 1,80p skill/scripts/teardown.py
    • rungrep -n aisa\|AISA_API_KEY\|max-call\|max-total skill/scripts/teardown.py
    • runhead -40
  • runbash -c cd "$(pwd)" && env | grep -i aisa; echo "env-exit=$?"; py...
    • runenv
    • rungrep -i aisa
    • runpython3 --version
    • runnpm --version
      • runnode /usr/bin/npm --version
        • secretread ~/.npmrc (its own config)

Exploration log

4 runs
  1. scripts:baseline ok · 1.2s

    no new behavior

  2. scripts:guided:LC_MESSAGES ok · 1.4s

    no new behavior

  3. scripts:ci-github ok · 1.0s

    no new behavior

  4. llm:baseline ok · 15.3s

    new behavior: ownread:./.env, ownread:~/.npmrc · 4 model steps, 6 commands

    $ cd "$(pwd)" && ls -la && ls -la skill && cat skill/SKILL.md | head -5 $ which aisa && aisa --version && aisa whoami 2>&1 | head -20 $ cd "$(pwd)" && command -v aisa; echo "exit=$?"; aisa --version 2>&1; echo "---"; cat README.md; echo "---"; cat package.json; echo "---"; ls src; echo "---"; cat .gitignore; echo "--- env keys:"; sed $ cd "$(pwd)" && ls skill/scripts skill/references && cat skill/_meta.json && cat skill/skill-card.md $ cd "$(pwd)" && sed -n '1,80p' skill/scripts/teardown.py; echo "..."; grep -n "aisa\|AISA_API_KEY\|max-call\|max-total" skill/scripts/teardown.py | head -40 $ cd "$(pwd)" && env | grep -i aisa; echo "env-exit=$?"; python3 --version; npm --version 2>&1 model said: I stopped before doing anything, because the skill's preconditions aren't met and I don't have a target site. **What's blocking** 1. **`aisa` CLI is not installed** — `command -v aisa` fails (`aisa: command not found`). The skill says to tell you to install it rather than install it unasked: ``` npm i -g @aisa-one/[email protected] aisa login ``` 2. **No `AISA_API_KEY`** in the environment.

scripts/scripts/teardown.py: 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.