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 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-composite
Source
clawhub 1.3.9
SHA-256
28e99b70aeb52297
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-composite 3 files · agent skill
  2. Install No install stepFiles were copied in as they are.
  3. Runs as ls -lawhich gtrkcat README.md package.json .env .gitignorels -la src skill An AI agent also used it 1 time.
  4. What it reached
    Network
    • registry.npmjs.org 2 connections, 828 B 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

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 package.json .env .gitignore; ls -la src sk...
    • runcat README.md package.json .env .gitignore
      • secretread ./.env
View full process tree
  • runbash -c pwd && ls -la
    • runls -la
  • runbash -c which gtrk && gtrk --version 2>&1 | head -5
    • runwhich gtrk
  • runbash -c cat README.md package.json .env .gitignore; ls -la src sk...
    • runcat README.md package.json .env .gitignore
      • secretread ./.env
    • runls -la src skill
  • runbash -c command -v gtrk; echo "---"; ls /usr/local/bin /usr/bin 2...
    • rungrep -i gtrk
    • runls /usr/local/bin /usr/bin
    • runnpm ls -g --depth=0
      • runnode /usr/bin/npm ls -g --depth=0
        • secretread ~/.npmrc (its own config)
  • runbash -c cat skill/_meta.json skill/skill-card.md; echo "=== src =...
    • runcat skill/_meta.json skill/skill-card.md
    • runcat src/index.js
    • rungit log --oneline
    • runhead -20
  • runbash -c find / -name "project.gtrk" -o -name "transcript.json" -o...
    • runhead -20
    • runfind / -name project.gtrk -o -name
    • rungrep -v proc
  • runbash -c node --version 2>&1; npm --version 2>&1; echo "---"; ls ~...
    • runnode --version
    • runnpm --version
      • runnode /usr/bin/npm --version
        • secretread ~/.npmrc (its own config)
    • runls ~/.gitruck
    • runenv
    • rungrep -i -E gitruck|gtrk
  • runbash -c cd /tmp && timeout 120 npm view @gitruck/cli version 2>&1...
    • runtail -5
    • runtimeout 120 npm view @gitruck/cli version
      • runnpm view @gitruck/cli version
        • runnode /usr/bin/npm view @gitruck/cli version
          • secretread ~/.npmrc (its own config)
  • runtimeout 120 npm view @gitruck/cli version
    • runnpm view @gitruck/cli version
      • runnode /usr/bin/npm view @gitruck/cli version
        • secretread ~/.npmrc (its own config)
  • runbash -c cd /tmp && timeout 60 npm view @gitruck/cli version > /tm...
    • runtimeout 60 npm view @gitruck/cli version
      • runnpm view @gitruck/cli version
        • runnode /usr/bin/npm view @gitruck/cli version
          • secretread ~/.npmrc (its own config)
          • netregistry.npmjs.org:443 sent 431 B
    • runcat /tmp/npmout.txt
    • runcat /tmp/npmerr.txt
  • runbash -c cd /tmp && timeout 60 npm view express version > /tmp/o.t...
    • runtimeout 60 npm view express version
      • runnpm view express version
        • runnode /usr/bin/npm view express version
          • secretread ~/.npmrc (its own config)
          • netregistry.npmjs.org:443 sent 397 B
          • netDNS lookups for npmjs.org 10 queries
    • runcat /tmp/o.txt
    • runcat /tmp/e.txt
    • runnpm config get registry
      • runnode /usr/bin/npm config get registry
        • secretread ~/.npmrc (its own config)

Exploration log

4 runs
  1. obedient:baseline ok · 1.6s

    no new behavior

    $ gtrk composite review --project <工程> --approve W01,W03 --reject W02 --adjust W04=80,90.9 --add 140,150 $ gtrk composite scaffold --project <工程> # 为已采纳窗口落场景骨架 composite/scenes/cp-wNN.html $ gtrk composite shots --project <工程> --material <素材 id 或文件> --around 246 --span 20 $ gtrk composite lay --project <工程> # 全量；--only cp-w03 只替换这颗 $ gtrk deps install --browser # 首次：装钉定版本的烘焙浏览器（约 110 MB）。MUST 先告诉用户再装 gtrk composite bake --project <工程> # 全部合成；--only cp-w03 只烤这颗
  2. obedient:declared-env ok · 2.0s

    no new behavior

    $ gtrk composite review --project <工程> --approve W01,W03 --reject W02 --adjust W04=80,90.9 --add 140,150 $ gtrk composite scaffold --project <工程> # 为已采纳窗口落场景骨架 composite/scenes/cp-wNN.html $ gtrk composite shots --project <工程> --material <素材 id 或文件> --around 246 --span 20 $ gtrk composite lay --project <工程> # 全量；--only cp-w03 只替换这颗 $ gtrk deps install --browser # 首次：装钉定版本的烘焙浏览器（约 110 MB）。MUST 先告诉用户再装 gtrk composite bake --project <工程> # 全部合成；--only cp-w03 只烤这颗
  3. obedient:ci-github ok · 2.1s

    no new behavior

    $ gtrk composite review --project <工程> --approve W01,W03 --reject W02 --adjust W04=80,90.9 --add 140,150 $ gtrk composite scaffold --project <工程> # 为已采纳窗口落场景骨架 composite/scenes/cp-wNN.html $ gtrk composite shots --project <工程> --material <素材 id 或文件> --around 246 --span 20 $ gtrk composite lay --project <工程> # 全量；--only cp-w03 只替换这颗 $ gtrk deps install --browser # 首次：装钉定版本的烘焙浏览器（约 110 MB）。MUST 先告诉用户再装 gtrk composite bake --project <工程> # 全部合成；--only cp-w03 只烤这颗
  4. llm:baseline ok · 142.1s

    new behavior: dns:registry.npmjs.org, ownread:./.env, ownread:~/.npmrc, write:~/.npm/_cacache/content-v2/sha512/9f/fe/* · token budget reached

    $ pwd && ls -la $ which gtrk && gtrk --version 2>&1 | head -5 $ cat README.md package.json .env .gitignore; ls -la src skill $ command -v gtrk; echo "---"; ls /usr/local/bin /usr/bin 2>/dev/null | grep -i gtrk; echo "---"; npm ls -g --depth=0 2>/dev/null $ cat skill/_meta.json skill/skill-card.md; echo "=== src ==="; cat src/index.js; echo "=== git ==="; git log --oneline | head -20 $ find / -name "project.gtrk" -o -name "transcript.json" -o -name "*.gtrk" 2>/dev/null | grep -v proc | head -20; echo "--- node/npm ---"; node --version; npm --version $ node --version 2>&1; npm --version 2>&1; echo "---"; ls ~/.gitruck 2>&1; echo "--- env ---"; env | grep -i -E "gitruck|gtrk" 2>&1 $ cd /tmp && timeout 120 npm view @gitruck/cli version 2>&1 | tail -5 $ cd /tmp && timeout 120 npm view @gitruck/cli version; echo "EXIT=$?" $ cd /tmp && timeout 60 npm view @gitruck/cli version > /tmp/npmout.txt 2>/tmp/npmerr.txt; echo "EXIT=$?"; echo "--- stdout ---"; cat /tmp/npmout.txt; echo "--- stderr ---"; cat /tmp/npmerr.txt model said: I'll start by exploring the project to understand what we're working with.

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.