Detonation LabsBehavioral security for the AI agent supply chain

Verdict

No malicious behavior observed

We ran it 1 time, with a normal setup. It contacted clawhub.ai and registry.npmjs.org. It read some credential files, but nothing it sent carried them.

4 findings. Scanned 27 Oct 2026 by detonator 0.5.1.

Target
zoom-cli
Source
clawhub 1.0.1
SHA-256
af2e26e53b08acfa
Files
3
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 1 run
  1. Package zoom-cli 3 files · agent skill
  2. Install No install scripts of its ownOnly the package manager ran.
  3. Runs as which zmhead -40ls -lawhich node npm An AI agent also used it 1 time.
  4. What it reached
    Network
    • clawhub.ai 1 connection, 96 B sent
    • registry.npmjs.org 9 connections, 2.1 KB sent
    Credentials
    • ./.envread
    • ~/.npmrcread
    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 a planted key with the service it belongs to (registry.npmjs.org)

Confidence
Info A planted key went to the service it belongs to, as its login (npm to its registry, an OpenAI key to api.openai.com).
Observed in
llm:baseline

Description

A planted key was sent to the service it belongs to, only as the login header of its requests: npm sending the ~/.npmrc token to registry.npmjs.org while installing, or an app calling api.openai.com with the OpenAI key from .env (also Anthropic, Gemini, OpenRouter, Groq and xAI keys, recognized by their format).

Impact

Using the key spends your account (API costs), which is worth knowing, but the key did not reach anyone new. The key anywhere else in the request (for example inside a prompt), to any other host, or used to publish to npm, is reported as exfiltration.

Evidence

~/.npmrc (npm) sent only as the login header of requests to registry.npmjs.org

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

clawhub.ai
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 sed)

Remediation

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

F04 Low

Agent read credential files (may be the agent's own choice)

Confidence
Info A credential file was opened by a program that does not own it.
Observed in
llm:baseline

Description

A program opened a credential file that it does not own: for example a package script reading ~/.npmrc, ~/.aws/credentials or ~/.ssh/id_rsa, rather than npm, the AWS CLI or ssh reading their own files. The reading program is named in the evidence. In this run the contents were not seen leaving the sandbox.

Impact

Reading credentials is the collection step that precedes theft. Exfiltration may be gated on conditions this run did not meet (a different date, CI variables, a reachable network), or the data may be staged for a later step.

Evidence

~/.npmrc (by cat, npm)

Remediation

Review why this package needs the file. Legitimate tools read only their own configuration; anything else should be treated as hostile until explained. Prefer running it with credentials unavailable (separate user, container, or scoped environment).

References

  • ATT&CK T1552.001 Credentials in Files
  • CWE-200 Exposure of Sensitive Information
  • OWASP MCP01:2025 Token Mismanagement & Secret Exposure

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 . && cat package.json; echo "--- README ---"; cat READ...
    • runsed s/=.*/=<redacted>/ .env
      • secretread ./.env
  • runbash -c cd . && timeout 30 curl -sS -o /dev/null -w 'npmjs=%{http...
    • runcat ~/.npmrc
      • secretread ~/.npmrc
View full process tree
  • runbash -c cd . && which zm && zm --version 2>&1 | head -5; echo "--...
    • runwhich zm
    • runhead -40
  • runbash -c cd . && ls -la; echo "--- node/npm ---"; which node npm 2...
    • runls -la
    • runwhich node npm
    • runnode --version
    • runnpm --version
      • runnode /usr/bin/npm --version
        • secretread ~/.npmrc (its own config)
    • runnpm ls -g --depth=0
      • runnode /usr/bin/npm ls -g --depth=0
        • secretread ~/.npmrc (its own config)
        • netregistry.npmjs.org:443 sent 431 B
    • runhead -20 ×2
    • runls ~/.npm-global/bin
    • runls /usr/local/bin
  • runbash -c cd . && cat package.json; echo "--- README ---"; cat READ...
    • runsed s/=.*/=<redacted>/ .env
      • secretread ./.env
    • runcat package.json
    • runcat README.md
    • runls -la src skill
    • rungit log --oneline -5
  • runbash -c cd . && cat skill/_meta.json; echo "--- card ---"; cat sk...
    • runcat skill/_meta.json
    • runcat skill/skill-card.md
    • runtail -5
    • runtimeout 60 npm view @wirecat/zoom-cli version
      • runnpm view @wirecat/zoom-cli version
        • runnode /usr/bin/npm view @wirecat/zoom-cli version
          • secretread ~/.npmrc (its own config)
          • netregistry.npmjs.org:443 sent 407 B
  • runbash -c cd . && timeout 60 npm view @wirecat/zoom-cli version 2>&...
    • runtimeout 60 npm view @wirecat/zoom-cli version
      • runnpm view @wirecat/zoom-cli version
        • runnode /usr/bin/npm view @wirecat/zoom-cli version
          • secretread ~/.npmrc (its own config)
          • netregistry.npmjs.org:443 sent 407 B
    • runnpm config get registry
      • runnode /usr/bin/npm config get registry
        • secretread ~/.npmrc (its own config)
    • runtimeout 20 curl -sS -o /dev/null
      • runcurl -sS -o /dev/null -w %{http_code}\n
        • netregistry.npmjs.org:443 sent 100 B
  • runbash -c cd . && timeout 30 curl -sS https://registry.npmjs.org/@w...
    • runhead -c 600
    • runtimeout 30 curl -sS https://registry.npmjs.org/@wirecat%2Fzoom-cli
      • runcurl -sS https://registry.npmjs.org/@wirecat%2Fzoom-cli
        • netregistry.npmjs.org:443 sent 100 B
    • runnode -e let s="";process.stdin.on("data",d=>s+=d).on("end",()=>{t...
    • runtimeout 30 curl -sS https://registry.npmjs.org/@wirecat%2Fzoom-cli
      • runcurl -sS https://registry.npmjs.org/@wirecat%2Fzoom-cli
        • netregistry.npmjs.org:443 sent 100 B
  • runbash -c cd . && timeout 30 curl -sS -o /dev/null -w 'npmjs=%{http...
    • runcat ~/.npmrc
      • secretread ~/.npmrc
    • runtimeout 30 curl -sS -o /dev/null
      • runcurl -sS -o /dev/null -w npmjs=%{http_code}\n
        • netregistry.npmjs.org:443 sent 88 B
    • runtimeout 30 curl -sS -o /dev/null
      • runcurl -sS -o /dev/null -w clawhub=%{http_code}\n
        • netclawhub.ai:443 sent 96 B
    • runenv
    • rungrep -iE proxy|npm_config|registry
    • runsed s/=.*/=<set>/
    • runsed s/=.*/=<redacted>/
    • runcat .npmrc
  • runbash -c cd . && timeout 30 curl -sS https://registry.npmjs.org/ex...
    • runtimeout 30 curl -sS https://registry.npmjs.org/express
      • runcurl -sS https://registry.npmjs.org/express
        • netregistry.npmjs.org:443 sent 88 B
    • runnode -e let s="";process.stdin.on("data",d=>s+=d).on("end",()=>{c...
    • runmkdir -p /tmp/zmtest
    • runtimeout 120 npm install --no-audit --no-fund
      • runnpm install --no-audit --no-fund @wirecat/zoom-cli
        • runnode /usr/bin/npm install --no-audit --no-fund @wirecat/zoom-cli
          • secretread ~/.npmrc (its own config)
          • netregistry.npmjs.org:443 sent 410 B
          • netDNS lookups for clawhub.ai, npmjs.org 20 queries
    • runtail -15

Exploration log

1 run
  1. llm:baseline ok · 66.9s

    new behavior: dns:clawhub.ai, dns:registry.npmjs.org, exec:curl, ownread:./.env · 8 model steps, 8 commands

    $ cd . && which zm && zm --version 2>&1 | head -5; echo "---"; zm doctor 2>&1 | head -40 $ cd . && ls -la; echo "--- node/npm ---"; which node npm 2>&1; node --version 2>&1; npm --version 2>&1; echo "--- global bins ---"; npm ls -g --depth=0 2>&1 | head -20; echo "--- search ---"; ls ~/.npm $ cd . && cat package.json; echo "--- README ---"; cat README.md; echo "--- .env (keys only) ---"; sed 's/=.*/=<redacted>/' .env; echo "--- src ---"; ls -la src skill; echo "--- git ---"; git log --onel $ cd . && cat skill/_meta.json; echo "--- card ---"; cat skill/skill-card.md; echo "--- npm view ---"; timeout 60 npm view @wirecat/zoom-cli version 2>&1 | tail -5 $ cd . && timeout 60 npm view @wirecat/zoom-cli version 2>&1; echo "exit=$?"; echo "--- registry ---"; npm config get registry; timeout 20 curl -sS -o /dev/null -w '%{http_code}\n' https://registry.npmj $ cd . && timeout 30 curl -sS https://registry.npmjs.org/@wirecat%2Fzoom-cli 2>&1 | head -c 600; echo; echo "---"; timeout 30 curl -sS https://registry.npmjs.org/@wirecat%2Fzoom-cli 2>&1 | node -e 'let $ cd . && timeout 30 curl -sS -o /dev/null -w 'npmjs=%{http_code}\n' https://registry.npmjs.org/express; timeout 30 curl -sS -o /dev/null -w 'clawhub=%{http_code}\n' https://clawhub.ai/wirecat/skills/zo $ cd . && timeout 30 curl -sS https://registry.npmjs.org/express | node -e 'let s="";process.stdin.on("data",d=>s+=d).on("end",()=>{const j=JSON.parse(s);console.log("express ok, latest:",j["dist-tags"] model said: The `npm view` returned nothing — let me check whether the registry is reachable at all.

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.