Verdict

No malicious behavior observed

We ran it 7 times, with a normal setup, TEST_DIR set and a GitHub Actions environment. It contacted registry.npmjs.org. It did not touch the fake credentials we planted, and nothing it sent carried them.

4 findings. Scanned 27 Oct 2026 by detonator 0.5.1.

Target: mermaid
Source: clawhub 1.0.0
SHA-256: 229c6756b5a05a43
Files: 6

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 7 runs

Package src 6 files · agent skill
Install No install scripts of its ownOnly the package manager ran.
Runs as bash <skill>/generate-test.shmktemp -dcatls -la An AI agent also used it 1 time.
What it reached
Network
- registry.npmjs.org 11 connections, 3.2 KB sent · during install
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 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

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

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 cat src/index.js; echo "--- env keys ---"; sed 's/=.*/=<r...
- runsed s/=.*/=<redacted>/ .env
  - secretread ./.env

View full process tree

runbash -c ls -la; echo "---"; ls -la skill; echo "---"; cat skill/S...
- runls -la
- runls -la skill
- runcat skill/SKILL.md
runbash -c cat README.md package.json .gitignore; echo "--- src ---"...
- runcat README.md package.json .gitignore
- runls -la src
- runcat skill/_meta.json skill/package.json skill/generate-test.sh
- runwhich mmdc
- runnode -v
- runnpm -v
  - runnode /usr/bin/npm -v
    - secretread ~/.npmrc (its own config)
runbash -c cat src/index.js; echo "--- env keys ---"; sed 's/=.*/=<r...
- runsed s/=.*/=<redacted>/ .env
  - secretread ./.env
- runcat src/index.js
runbash -c npm install -g @mermaid-js/mermaid-cli 2>&1 | tail -20; w...
- runtail -20
- runnpm install -g @mermaid-js/mermaid-cli
  - runnode /usr/bin/npm install -g @mermaid-js/mermaid-cli
    - secretread ~/.npmrc (its own config)
    - netregistry.npmjs.org:443 sent 436 B
    - netregistry.npmjs.org:443 sent 422 B
- runwhich mmdc
runbash -c npm config get registry; echo "---"; timeout 30 npm view ...
- runnpm config get registry
  - runnode /usr/bin/npm config get registry
    - secretread ~/.npmrc (its own config)
- runtail -5
- runtimeout 30 npm view @mermaid-js/mermaid-cli version
  - runnpm view @mermaid-js/mermaid-cli version
    - runnode /usr/bin/npm view @mermaid-js/mermaid-cli version
      - secretread ~/.npmrc (its own config)
      - netregistry.npmjs.org:443 sent 419 B
- runwhich chromium chromium-browser google-chrome
- runls ~/.cache/puppeteer
- runls node_modules
- runhead
runbash -c timeout 30 npm view @mermaid-js/mermaid-cli version; echo...
- runtimeout 30 npm view @mermaid-js/mermaid-cli version
  - runnpm view @mermaid-js/mermaid-cli version
    - runnode /usr/bin/npm view @mermaid-js/mermaid-cli version
      - secretread ~/.npmrc (its own config)
      - netregistry.npmjs.org:443 sent 419 B
- runtimeout 15 curl -sS -o /dev/null
  - runcurl -sS -o /dev/null -w %{http_code}\n
    - netregistry.npmjs.org:443 sent 106 B
runbash -c timeout 30 npm view @mermaid-js/mermaid-cli version --log...
- runtimeout 30 npm view @mermaid-js/mermaid-cli version
  - runnpm view @mermaid-js/mermaid-cli version --loglevel=silly
    - runnode /usr/bin/npm view @mermaid-js/mermaid-cli version --loglevel=silly
      - secretread ~/.npmrc (its own config)
      - netregistry.npmjs.org:443 sent 419 B
- runtail -30
runbash -c timeout 20 curl -sS https://registry.npmjs.org/@mermaid-j...
- runtimeout 20 curl -sS https://registry.npmjs.org/@mermaid-js%2fmermaid-cli
  - runcurl -sS https://registry.npmjs.org/@mermaid-js%2fmermaid-cli
    - netregistry.npmjs.org:443 sent 106 B
- runhead -c 600
- runtimeout 20 curl -sS https://registry.npmjs.org/@mermaid-js%2fmermaid-cli
  - runcurl -sS https://registry.npmjs.org/@mermaid-js%2fmermaid-cli
    - netregistry.npmjs.org:443 sent 106 B
- runwc -c
runbash -c cd /tmp && timeout 60 npm install --no-save --prefix /tmp...
- runtail -5
- runtimeout 60 npm install --no-save --prefix
  - runnpm install --no-save --prefix /tmp/mmdtest @mermaid-js/mermaid-cli
    - runnode /usr/bin/npm install --no-save --prefix /tmp/mmdtest
      - secretread ~/.npmrc (its own config)
      - netregistry.npmjs.org:443 sent 422 B
- runtimeout 30 npm view mermaid version
  - runnpm view mermaid version
    - runnode /usr/bin/npm view mermaid version
      - secretread ~/.npmrc (its own config)
      - netregistry.npmjs.org:443 sent 385 B
- runtail -3
- runhead -c 300
- runtimeout 20 curl -sS https://registry.npmjs.org/mermaid
  - runcurl -sS https://registry.npmjs.org/mermaid
    - netregistry.npmjs.org:443 sent 88 B
    - netDNS lookups for npmjs.org 20 queries

Exploration log

7 runs

scripts:baseline ok · 1.3s

no new behavior
scripts:guided:TEST_DIR ok · 0.5s

no new behavior
scripts:ci-github ok · 0.5s

no new behavior
obedient:baseline ok · 0.4s

no new behavior

$ mmdc -i input.mmd -o output.png -t dark -b transparent
obedient:guided:TEST_DIR ok · 0.4s

no new behavior

$ mmdc -i input.mmd -o output.png -t dark -b transparent
obedient:ci-github ok · 0.4s

no new behavior

$ mmdc -i input.mmd -o output.png -t dark -b transparent
llm:baseline ok · 60.2s

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

$ ls -la; echo "---"; ls -la skill; echo "---"; cat skill/SKILL.md $ cat README.md package.json .gitignore; echo "--- src ---"; ls -la src; echo "--- skill meta ---"; cat skill/_meta.json skill/package.json skill/generate-test.sh; echo "--- mmdc ---"; which mmdc || ech $ cat src/index.js; echo "--- env keys ---"; sed 's/=.*/=<redacted>/' .env $ npm install -g @mermaid-js/mermaid-cli 2>&1 | tail -20; which mmdc $ npm config get registry; echo "---"; timeout 30 npm view @mermaid-js/mermaid-cli version 2>&1 | tail -5; echo "--- puppeteer/chromium present? ---"; which chromium chromium-browser google-chrome 2>/de $ timeout 30 npm view @mermaid-js/mermaid-cli version; echo "exit=$?"; echo "--- connectivity ---"; timeout 15 curl -sS -o /dev/null -w "%{http_code}\n" https://registry.npmjs.org/@mermaid-js%2fmermaid- $ timeout 30 npm view @mermaid-js/mermaid-cli version --loglevel=silly 2>&1 | tail -30 $ timeout 20 curl -sS https://registry.npmjs.org/@mermaid-js%2fmermaid-cli | head -c 600; echo; echo "--- size ---"; timeout 20 curl -sS https://registry.npmjs.org/@mermaid-js%2fmermaid-cli | wc -c $ cd /tmp && timeout 60 npm install --no-save --prefix /tmp/mmdtest @mermaid-js/mermaid-cli 2>&1 | tail -5; echo "---"; timeout 30 npm view mermaid version 2>&1 | tail -3; echo "---"; timeout 20 curl -s model said: The registry responds 200 but npm parses no versions. Let me inspect the actual response body.

scripts/generate-test.sh: coverage plateau (2 runs with no new behavior); obedient: 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.