Verdict

No malicious behavior observed

We ran it 4 times, with a normal setup, the environment variables it says it needs and a GitHub Actions environment. It contacted github.com and 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: gtrk-music-visualizer
Source: clawhub 1.3.9
SHA-256: fa9dee43e0cdc265
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 4 runs

Package gtrk-music-visualizer 3 files · agent skill
Install No install stepFiles were copied in as they are.
Runs as ls -lahead -50sed s/=.*/=<redacted>/ .envcat README.md package.json .gitignore An AI agent also used it 1 time.
What it reached
Network
- github.com 1 connection, 84 B sent
- registry.npmjs.org 10 connections, 2.1 KB sent
Credentials
- ./.envread
~/.npmrc read by its own tool (normal)
Files written
- ./cli.tgzwritten

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

github.com

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 cd "$(pwd)" && cat README.md package.json .gitignore && e...
- runsed s/=.*/=<redacted>/ .env
  - secretread ./.env

View full process tree

runbash -c cd "$(pwd)" && ls -la && echo "--- doctor ---" && gtrk do...
- runls -la
- runhead -50
runbash -c cd "$(pwd)" && cat README.md package.json .gitignore && e...
- runsed s/=.*/=<redacted>/ .env
  - secretread ./.env
- runcat README.md package.json .gitignore
- runls -la src skill
- runnode -v
- runnpm -v
  - runnode /usr/bin/npm -v
    - secretread ~/.npmrc (its own config)
runbash -c cd "$(pwd)" && cat skill/_meta.json skill/skill-card.md &...
- runcat skill/_meta.json skill/skill-card.md
- runfind / -maxdepth 6 ( -iname
- runhead -20
runbash -c npm i -g @gitruck/cli@latest 2>&1 | tail -15; echo "--- w...
- runtail -15
- runnpm i -g @gitruck/cli@latest
  - runnode /usr/bin/npm i -g @gitruck/cli@latest
    - secretread ~/.npmrc (its own config)
    - netregistry.npmjs.org:443 sent 456 B
    - netregistry.npmjs.org:443 sent 436 B
- runwhich gtrk
- runhead -5
runbash -c npm config get registry; echo "--- view ---"; npm view @g...
- runnpm config get registry
  - runnode /usr/bin/npm config get registry
    - secretread ~/.npmrc (its own config)
- runnpm view @gitruck/cli version
  - runnode /usr/bin/npm view @gitruck/cli version
    - secretread ~/.npmrc (its own config)
    - netregistry.npmjs.org:443 sent 397 B
- runtail -10
- runtimeout 15 npm ping
  - runnpm ping
    - runnode /usr/bin/npm ping
      - secretread ~/.npmrc (its own config)
      - netregistry.npmjs.org:443 sent 286 B
- runtail -5
runbash -c timeout 20 curl -s -o /dev/null -w "gitruck-cli: %{http_c...
- runtimeout 20 curl -s -o /dev/null
  - runcurl -s -o /dev/null -w gitruck-cli: %{http_code}\n
    - netregistry.npmjs.org:443 sent 95 B
- runtimeout 20 curl -s -o /dev/null
  - runcurl -s -o /dev/null -w express(control): %{http_code}\n
    - netregistry.npmjs.org:443 sent 88 B
- runtimeout 20 curl -s https://registry.npmjs.org/@gitruck%2Fcli
  - runcurl -s https://registry.npmjs.org/@gitruck%2Fcli
    - netregistry.npmjs.org:443 sent 95 B
- runhead -c 300
runbash -c timeout 20 curl -s https://registry.npmjs.org/@gitruck%2F...
- runtimeout 20 curl -s https://registry.npmjs.org/@gitruck%2Fcli/latest
  - runcurl -s https://registry.npmjs.org/@gitruck%2Fcli/latest
    - netregistry.npmjs.org:443 sent 102 B
- runhead -c 300
- runtimeout 20 curl -s -o /dev/null
  - runcurl -s -o /dev/null -w %{http_code}\n
    - netregistry.npmjs.org:443 sent 109 B
- runtimeout 20 curl -s -o /dev/null
  - runcurl -s -o /dev/null -w github: %{http_code}\n
    - netgithub.com:443 sent 84 B
runbash -c cd /tmp && rm -rf gtrkprobe && mkdir gtrkprobe && cd gtrk...
- runrm -rf gtrkprobe
- runmkdir gtrkprobe
- runtimeout 30 curl -s -o cli.tgz
  - runcurl -s -o cli.tgz https://registry.npmjs.org/@gitruck/cli/-/cli-1.0.0.tgz
    - netregistry.npmjs.org:443 sent 109 B
    - filewrote ./cli.tgz
    - netDNS lookups for github.com, npmjs.org 22 queries
- runls -l cli.tgz
- runfile cli.tgz
- runhead -c 200 cli.tgz
- runhead -5
- runxxd

Exploration log

4 runs

obedient:baseline ok · 0.9s

no new behavior

$ gtrk music-visualizer <音频> --template <模板id> [可选样式/文件] [--json] $ gtrk patch move --project <dir> --clip <clip_id> --to 5.0 gtrk patch trim --project <dir> --clip <clip_id> --out -1s
obedient:declared-env ok · 0.6s

no new behavior

$ gtrk music-visualizer <音频> --template <模板id> [可选样式/文件] [--json] $ gtrk patch move --project <dir> --clip <clip_id> --to 5.0 gtrk patch trim --project <dir> --clip <clip_id> --out -1s
obedient:ci-github ok · 0.6s

no new behavior

$ gtrk music-visualizer <音频> --template <模板id> [可选样式/文件] [--json] $ gtrk patch move --project <dir> --clip <clip_id> --to 5.0 gtrk patch trim --project <dir> --clip <clip_id> --out -1s
llm:baseline ok · 64.2s

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

$ cd "$(pwd)" && ls -la && echo "--- doctor ---" && gtrk doctor 2>&1 | head -50 $ cd "$(pwd)" && cat README.md package.json .gitignore && echo "--- env keys ---" && sed 's/=.*/=<redacted>/' .env && echo "--- src ---" && ls -la src skill && echo "--- node ---" && node -v 2>&1; npm - $ cd "$(pwd)" && cat skill/_meta.json skill/skill-card.md && echo "--- audio search ---" && find / -maxdepth 6 \( -iname '*.mp3' -o -iname '*.wav' -o -iname '*.m4a' -o -iname '*.flac' -o -iname '*.aac' $ npm i -g @gitruck/cli@latest 2>&1 | tail -15; echo "--- which ---"; which gtrk 2>&1; gtrk --version 2>&1 | head -5 $ npm config get registry; echo "--- view ---"; npm view @gitruck/cli version 2>&1 | tail -10; echo "--- ping ---"; timeout 15 npm ping 2>&1 | tail -5 $ timeout 20 curl -s -o /dev/null -w "gitruck-cli: %{http_code}\n" https://registry.npmjs.org/@gitruck%2Fcli; timeout 20 curl -s -o /dev/null -w "express(control): %{http_code}\n" https://registry.npmjs $ timeout 20 curl -s https://registry.npmjs.org/@gitruck%2Fcli/latest | head -c 300; echo; echo "--- tarball guess ---"; timeout 20 curl -s -o /dev/null -w "%{http_code}\n" https://registry.npmjs.org/@g $ cd /tmp && rm -rf gtrkprobe && mkdir gtrkprobe && cd gtrkprobe && timeout 30 curl -s -o cli.tgz https://registry.npmjs.org/@gitruck/cli/-/cli-1.0.0.tgz && ls -l cli.tgz && file cli.tgz && head -c 200 model said: The tarball URL returns 200. Let me inspect what it actually contains before trusting it.

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.