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

Verdict

No malicious behavior observed

We ran it 1 time, with a normal setup. It contacted registry.npmjs.org. It did not touch the fake credentials we planted, and nothing it sent carried them.

4 findings. Scanned 26 Oct 2026 by detonator 0.5.1.

Target
reelary-find-footage
Source
clawhub 0.1.0
SHA-256
eec0372f8f908752
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 1 run
  1. Package find-footage 3 files · agent skill
  2. Install No install stepFiles were copied in as they are.
  3. Runs as ls -lals -la skillcat skill/SKILL.mdhead -50 An AI agent also used it 1 time.
  4. What it reached
    Network
    • registry.npmjs.org 6 connections, 1.5 KB sent
    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

Used the planted login with its own service (registry.npmjs.org)

Confidence
Info A planted login went to the service it belongs to, as normal authentication (npm sending its token to registry.npmjs.org while installing).
Observed in
llm:baseline

Description

A planted login was sent to the service it belongs to, only as the Authorization header of ordinary requests: for example npm sending the ~/.npmrc token to registry.npmjs.org while installing dependencies.

Impact

None in itself: this is how the package manager authenticates. Publishing, unpublishing or creating tokens with it would be reported as exfiltration.

Evidence

~/.npmrc (npm) sent only as the login header of ordinary requests (no publish)

Remediation

No action needed.

F02 Low

Network destinations contacted

Confidence
Info The package connected to these hosts.
Observed in
llm:baseline

Description

Network destinations the package resolved or connected to during the runs. All traffic was captured by the sandbox; nothing reached the internet.

Impact

Context only. Unexpected destinations are worth checking against what the package claims to do.

Evidence

registry.npmjs.org

Remediation

Confirm each host is expected (the package's API, its registry). Allowlist expected egress in production.

F03 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 cat)

Remediation

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

F04 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, npx)

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 cat package.json; echo "--- README"; cat README.md; echo ...
    • runcat .env
      • secretread ./.env
View full process tree
  • runbash -c ls -la; echo "---"; ls -la skill 2>/dev/null; echo "---";...
    • runls -la
    • runls -la skill
    • runcat skill/SKILL.md
    • runhead -50
  • runbash -c which npx node; echo "---"; npx -y reelary --version 2>&1...
    • runwhich npx node
    • runhead -20
    • runnpx -y reelary --version
      • runnode /usr/bin/npx -y reelary --version
        • secretread ~/.npmrc (its own config)
        • netregistry.npmjs.org:443 sent 433 B
        • netregistry.npmjs.org:443 sent 441 B
  • runbash -c cat package.json; echo "--- README"; cat README.md; echo ...
    • runcat .env
      • secretread ./.env
    • runcat package.json
    • runcat README.md
    • runls -la src
    • runcat skill/_meta.json
    • runcat skill/skill-card.md
  • runbash -c ls ~/.reelary ~/Library/Application\ Support/Reelary 2>&1...
    • runhead
    • runls ~/.reelary ~/Library/Application Support/Reelary
    • runhead -20 ×2
    • runfind / -maxdepth 4 -iname *reelary*
    • runfind ~ -maxdepth 3 ( -iname
  • runbash -c npm view reelary version 2>&1 | head -5; echo "--- regist...
    • runnpm view reelary version
      • runnode /usr/bin/npm view reelary version
        • secretread ~/.npmrc (its own config)
        • netregistry.npmjs.org:443 sent 385 B
    • runhead -5
    • runnpm config get registry
      • runnode /usr/bin/npm config get registry
        • secretread ~/.npmrc (its own config)
    • runcurl -s -m 8 -o /dev/null
      • netregistry.npmjs.org:443 sent 88 B
  • runbash -c curl -s -m 10 https://registry.npmjs.org/reelary | head -...
    • runcurl -s -m 10 https://registry.npmjs.org/reelary
      • netregistry.npmjs.org:443 sent 88 B
    • runhead -c 400
    • runcurl -s -m 10 https://registry.npmjs.org/-/v1/search?text=reelary&size=5
      • netregistry.npmjs.org:443 sent 112 B
      • netDNS lookups for npmjs.org 10 queries
    • runhead -c 600

Exploration log

1 run
  1. llm:baseline ok · 49.4s

    new behavior: dns:registry.npmjs.org, exec:curl, ownread:./.env, ownread:~/.npmrc · 5 model steps, 6 commands

    $ ls -la; echo "---"; ls -la skill 2>/dev/null; echo "---"; cat skill/SKILL.md 2>/dev/null | head -50 $ which npx node; echo "---"; npx -y reelary --version 2>&1 | head -20 $ cat package.json; echo "--- README"; cat README.md; echo "--- .env"; cat .env; echo "--- src"; ls -la src; echo "--- meta"; cat skill/_meta.json; echo; cat skill/skill-card.md $ ls ~/.reelary ~/Library/Application\ Support/Reelary 2>&1 | head; echo "---"; find / -maxdepth 4 -iname "*reelary*" 2>/dev/null | head -20; echo "--- media"; find ~ -maxdepth 3 \( -iname "*.mp4" -o -i $ npm view reelary version 2>&1 | head -5; echo "--- registry"; npm config get registry; echo "--- net"; curl -s -m 8 -o /dev/null -w "%{http_code}\n" https://registry.npmjs.org/reelary 2>&1 $ curl -s -m 10 https://registry.npmjs.org/reelary | head -c 400; echo; echo "--- search"; curl -s -m 10 "https://registry.npmjs.org/-/v1/search?text=reelary&size=5" | head -c 600 model said: I stopped before running any searches. Here's why. **What I found** - The `find-footage` skill is installed at `./skill`, but it's a thin wrapper: every action depends on the Reelary app/CLI (`reelary_search`, `npx -y reelary search ...`). - Reelary isn't installed here, and the `reelary` package doesn't exist on npm (`ENOVERSIONS`), so the documented fallback can't run. - There's no Reelary ind

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.