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, 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-live-slicing
Source
clawhub 1.3.9
SHA-256
6b41c8821a0f1eb6
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
  1. Package gtrk-live-slicing 3 files · agent skill
  2. Install No install scripts of its ownOnly the package manager ran.
  3. Runs as ls -lals -la skillhead -50which gtrk ffmpeg ffprobe An AI agent also used it 1 time.
  4. What it reached
    Network
    • github.com 2 connections, 479 B sent
    • registry.npmjs.org 7 connections, 1.6 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 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 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)

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 README.md; echo "--- package.json"; cat package.json;...
    • runcat .env
      • secretread ./.env
View full process tree
  • runbash -c pwd; ls -la; echo "---"; ls -la skill 2>/dev/null | head ...
    • runls -la
    • runls -la skill
    • runhead -50
  • runbash -c which gtrk ffmpeg ffprobe; echo "---"; gtrk --version 2>&...
    • runwhich gtrk ffmpeg ffprobe
    • runhead -5
  • runbash -c cat README.md; echo "--- package.json"; cat package.json;...
    • runcat .env
      • secretread ./.env
    • runcat README.md
    • runcat package.json
    • runls -la src
    • runcat .gitignore
  • runbash -c cat skill/_meta.json; echo "---"; cat skill/skill-card.md
    • runcat skill/_meta.json
    • runcat skill/skill-card.md
  • runbash -c cat src/index.js; echo "--- git log"; git log --oneline |...
    • runcat src/index.js
    • rungit log --oneline
    • runhead -10
    • runfind / -xdev ( -iname *.mp4
    • runhead -20
  • runbash -c ls ~/.gitruck 2>/dev/null; echo "--- env"; env | grep -i ...
    • runls ~/.gitruck
    • runenv
    • rungrep -i -E gitruck|gtrk
    • 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
    • runnode --version
    • runnpm --version
      • runnode /usr/bin/npm --version
        • secretread ~/.npmrc (its own config)
  • runbash -c cd /tmp && timeout 120 npm install -g @gitruck/cli 2>&1 |...
    • runtail -20
    • runtimeout 120 npm install -g @gitruck/cli
      • runnpm install -g @gitruck/cli
        • runnode /usr/bin/npm install -g @gitruck/cli
          • secretread ~/.npmrc (its own config)
          • netregistry.npmjs.org:443 sent 400 B
    • runwhich gtrk
  • runbash -c cd /tmp && timeout 60 npm view @gitruck/cli 2>&1 | head -...
    • runhead -20
    • runtimeout 60 npm view @gitruck/cli
      • runnpm view @gitruck/cli
        • runnode /usr/bin/npm view @gitruck/cli
          • secretread ~/.npmrc (its own config)
          • netregistry.npmjs.org:443 sent 397 B
    • runnpm config get registry
      • runnode /usr/bin/npm config get registry
        • secretread ~/.npmrc (its own config)
    • runtimeout 10 curl -sS -o /dev/null
      • runcurl -sS -o /dev/null -w %{http_code}\n
        • netregistry.npmjs.org:443 sent 81 B
  • runbash -c cd /tmp && timeout 60 curl -sS https://registry.npmjs.org...
    • runhead -c 500
    • runtimeout 60 curl -sS https://registry.npmjs.org/@gitruck%2Fcli
      • runcurl -sS https://registry.npmjs.org/@gitruck%2Fcli
        • netregistry.npmjs.org:443 sent 95 B
    • runtimeout 30 curl -sS -o /dev/null
      • runcurl -sS -o /dev/null -w %{http_code}\n
        • netgithub.com:443 sent 84 B
  • runbash -c cd /tmp && timeout 60 curl -sS https://registry.npmjs.org...
    • runtimeout 60 curl -sS https://registry.npmjs.org/gtrk
      • runcurl -sS https://registry.npmjs.org/gtrk
        • netregistry.npmjs.org:443 sent 85 B
    • runhead -c 300
    • runhead -c 800
    • runtimeout 60 curl -sS https://registry.npmjs.org/-/v1/search?text=gitruck&size=10
      • runcurl -sS https://registry.npmjs.org/-/v1/search?text=gitruck&size=10
        • netregistry.npmjs.org:443 sent 113 B
  • runbash -c cd /tmp && timeout 60 git clone --depth 1 https://github....
    • runtimeout 60 git clone --depth 1
      • rungit clone --depth 1 https://github.com/Gitruck/cli
        • run/usr/lib/git-core/git remote-https origin https://github.com/Gitruck/cli
          • run/usr/lib/git-core/git-remote-https origin https://github.com/Gitruck/cli
            • netgithub.com:443 sent 395 B
            • netDNS lookups for github.com, npmjs.org 18 queries
    • runtail -5
    • runhead
    • runls /tmp/cli

Exploration log

4 runs
  1. obedient:baseline ok · 1.1s

    no new behavior

    $ ffmpeg -ss 3600 -t 2400 -i "<直播回放>" -c copy "<工作区>/inputs/<名>_seg02_60-100min.mp4" $ gtrk oralcut-result <task_id> --out <目录> # task_id 在产物根 task.json；--out 必填 $ gtrk subtitle lay --gtrk "<产物根>/clip{i}/gtrk/<该 clip 的 .gtrk>" --transcript "<产物根>/json/transcript.json" --language <该段提交时的源语种> $ gtrk project background --gtrk "<产物根>/clip{i}/gtrk/<该 clip 的 .gtrk>" --blur
  2. obedient:declared-env ok · 0.7s

    no new behavior

    $ ffmpeg -ss 3600 -t 2400 -i "<直播回放>" -c copy "<工作区>/inputs/<名>_seg02_60-100min.mp4" $ gtrk oralcut-result <task_id> --out <目录> # task_id 在产物根 task.json；--out 必填 $ gtrk subtitle lay --gtrk "<产物根>/clip{i}/gtrk/<该 clip 的 .gtrk>" --transcript "<产物根>/json/transcript.json" --language <该段提交时的源语种> $ gtrk project background --gtrk "<产物根>/clip{i}/gtrk/<该 clip 的 .gtrk>" --blur
  3. obedient:ci-github ok · 1.0s

    no new behavior

    $ ffmpeg -ss 3600 -t 2400 -i "<直播回放>" -c copy "<工作区>/inputs/<名>_seg02_60-100min.mp4" $ gtrk oralcut-result <task_id> --out <目录> # task_id 在产物根 task.json；--out 必填 $ gtrk subtitle lay --gtrk "<产物根>/clip{i}/gtrk/<该 clip 的 .gtrk>" --transcript "<产物根>/json/transcript.json" --language <该段提交时的源语种> $ gtrk project background --gtrk "<产物根>/clip{i}/gtrk/<该 clip 的 .gtrk>" --blur
  4. llm:baseline ok · 79.9s

    new behavior: dns:github.com, dns:registry.npmjs.org, exec:curl, ownread:./.env · token budget reached

    $ pwd; ls -la; echo "---"; ls -la skill 2>/dev/null | head -50 $ which gtrk ffmpeg ffprobe; echo "---"; gtrk --version 2>&1 | head -5 $ cat README.md; echo "--- package.json"; cat package.json; echo "--- .env"; cat .env; echo "--- src"; ls -la src; echo "--- gitignore"; cat .gitignore $ cat skill/_meta.json; echo "---"; cat skill/skill-card.md $ cat src/index.js; echo "--- git log"; git log --oneline | head -10; echo "--- find media"; find / -xdev \( -iname "*.mp4" -o -iname "*.ts" -o -iname "*.flv" -o -iname "*.mkv" -o -iname "*.mov" -o -ina $ ls ~/.gitruck 2>/dev/null; echo "--- env"; env | grep -i -E "gitruck|gtrk" ; echo "--- npm"; npm ls -g --depth=0 2>/dev/null; node --version; npm --version $ cd /tmp && timeout 120 npm install -g @gitruck/cli 2>&1 | tail -20; echo "EXIT:$?"; which gtrk $ cd /tmp && timeout 60 npm view @gitruck/cli 2>&1 | head -20; echo "---registry"; npm config get registry; echo "--- net"; timeout 10 curl -sS -o /dev/null -w "%{http_code}\n" https://registry.npmjs.or $ cd /tmp && timeout 60 curl -sS https://registry.npmjs.org/@gitruck%2Fcli 2>&1 | head -c 500; echo; echo "---"; timeout 30 curl -sS -o /dev/null -w "%{http_code}\n" https://github.com/Gitruck/cli $ cd /tmp && timeout 60 curl -sS https://registry.npmjs.org/gtrk 2>&1 | head -c 300; echo; echo "--- search"; timeout 60 curl -sS "https://registry.npmjs.org/-/v1/search?text=gitruck&size=10" 2>&1 | hea model said: I'll start by looking at the project directory and checking what's available.

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.