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-travel-recap
Source: clawhub 1.3.9
SHA-256: 6ac7058609b2d083
Files: 4

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-travel-recap 4 files · agent skill
Install No install scripts of its ownOnly the package manager ran.
Runs as ls -lals -la ./skillwhich gtrkhead -5 An AI agent also used it 1 time.
What it reached
Network
- registry.npmjs.org 5 connections, 1.1 KB sent
Credentials
- ./.envread
~/.npmrc read by its own tool (normal)
Files written
- ./--jsonwritten
- ./.git/index.lockwritten

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; echo "---PKG---"; cat package.json; echo "...
- runcat .env
  - secretread ./.env

View full process tree

runbash -c pwd; ls -la; echo "---SKILL---"; ls -la ./skill 2>/dev/null
- runls -la
- runls -la ./skill
runbash -c which gtrk; gtrk --version 2>&1 | head -5; echo "---"; ls...
- runwhich gtrk
- runhead -5
- runls ~/.gitruck
runbash -c cat README.md; echo "---PKG---"; cat package.json; echo "...
- runcat .env
  - secretread ./.env
- runcat README.md
- runcat package.json
- runls -la src
- runcat .gitignore
runbash -c ls -la skill/references; echo "---META---"; cat skill/_me...
- runls -la skill/references
- 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 -10
- rungit status --short
  - filewrote ./.git/index.lock
- runhead -20
runbash -c which node npm ffmpeg ffprobe 2>&1; echo "---"; node --ve...
- runwhich node npm ffmpeg ffprobe
- runnode --version
- runnpm --version
  - runnode /usr/bin/npm --version
    - secretread ~/.npmrc (its own config)
- runtimeout 8 curl -sS -o /dev/null
  - runcurl -sS -o /dev/null -w %{http_code}\n
    - netregistry.npmjs.org:443 sent 93 B
runbash -c cd /var/tmp && timeout 180 npm install -g @gitruck/cli 2>...
- runtimeout 180 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 436 B
      - netregistry.npmjs.org:443 sent 400 B
- runtail -20
- runwhich gtrk
- runhead -3
runbash -c timeout 20 curl -sS https://registry.npmjs.org/@gitruck%2...
- runhead -c 600
- runtimeout 20 curl -sS https://registry.npmjs.org/@gitruck%2Fcli
  - runcurl -sS https://registry.npmjs.org/@gitruck%2Fcli
    - netregistry.npmjs.org:443 sent 95 B
- runhead -c 800
- runtimeout 20 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
    - netDNS lookups for npmjs.org 8 queries

Exploration log

4 runs

obedient:baseline ok · 1.6s

new behavior: write:./--json

$ ① 理解 transcript 原片（二创）/ matrix index + describe（原创） ①′ 适配闸【必过】读 ① 的既有产物判题材（见 §一′）——不是旅拍就硬停，MUST NOT 进入写稿 ② 写稿三段式规约（见 §三）→ 解说稿 + 标题 + HashTag ③ 检查点① 【必停】稿件确认 · 画幅 · 音色 · BGM（gtrk mat $ 判这一帧对旅拍短视频有没有「看点」，0-100： - 奇观地貌：雅丹/冰川/星空/沙漠/峡谷等罕见地形 - 极端天候光线：日出日落、逆光、雪雾、暴雨、极光 - 人文场面密度：市集、节庆、宗教仪式、当地人劳作 - 反差罕见：人与巨大景观的比例、无人区里的人造物、动物 - 规模感：能看出「有多大/有多高/有多远」的构图低分：车内挡风玻璃前方公路、酒店房间、无主体的天空、拍糊的中间帧 $ gtrk matrix describe --plan <工程>/split/broll-plan.json --highlight-rubric @<工程>/highlight-rubric.txt $ gtrk matrix lay --project "<工程目录>" --arrange-estimate-only --json # 停在计价确认之前：零云端调用、工程文件零改动 $ gtrk transcript "<原片>" --lang <zh-CN 普通话 | zh-HK 粤语 | en-US | ja-JP …> --json -o "<工程目录>/transcript/<片名>-transcript.md" gtrk matrix material "<情绪+地理文化检索词>" --scope audio --top-k 5 --diversity --json g $ 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 · 2.1s

no new behavior

$ ① 理解 transcript 原片（二创）/ matrix index + describe（原创） ①′ 适配闸【必过】读 ① 的既有产物判题材（见 §一′）——不是旅拍就硬停，MUST NOT 进入写稿 ② 写稿三段式规约（见 §三）→ 解说稿 + 标题 + HashTag ③ 检查点① 【必停】稿件确认 · 画幅 · 音色 · BGM（gtrk mat $ 判这一帧对旅拍短视频有没有「看点」，0-100： - 奇观地貌：雅丹/冰川/星空/沙漠/峡谷等罕见地形 - 极端天候光线：日出日落、逆光、雪雾、暴雨、极光 - 人文场面密度：市集、节庆、宗教仪式、当地人劳作 - 反差罕见：人与巨大景观的比例、无人区里的人造物、动物 - 规模感：能看出「有多大/有多高/有多远」的构图低分：车内挡风玻璃前方公路、酒店房间、无主体的天空、拍糊的中间帧 $ gtrk matrix describe --plan <工程>/split/broll-plan.json --highlight-rubric @<工程>/highlight-rubric.txt $ gtrk matrix lay --project "<工程目录>" --arrange-estimate-only --json # 停在计价确认之前：零云端调用、工程文件零改动 $ gtrk transcript "<原片>" --lang <zh-CN 普通话 | zh-HK 粤语 | en-US | ja-JP …> --json -o "<工程目录>/transcript/<片名>-transcript.md" gtrk matrix material "<情绪+地理文化检索词>" --scope audio --top-k 5 --diversity --json g $ 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 · 2.0s

no new behavior

$ ① 理解 transcript 原片（二创）/ matrix index + describe（原创） ①′ 适配闸【必过】读 ① 的既有产物判题材（见 §一′）——不是旅拍就硬停，MUST NOT 进入写稿 ② 写稿三段式规约（见 §三）→ 解说稿 + 标题 + HashTag ③ 检查点① 【必停】稿件确认 · 画幅 · 音色 · BGM（gtrk mat $ 判这一帧对旅拍短视频有没有「看点」，0-100： - 奇观地貌：雅丹/冰川/星空/沙漠/峡谷等罕见地形 - 极端天候光线：日出日落、逆光、雪雾、暴雨、极光 - 人文场面密度：市集、节庆、宗教仪式、当地人劳作 - 反差罕见：人与巨大景观的比例、无人区里的人造物、动物 - 规模感：能看出「有多大/有多高/有多远」的构图低分：车内挡风玻璃前方公路、酒店房间、无主体的天空、拍糊的中间帧 $ gtrk matrix describe --plan <工程>/split/broll-plan.json --highlight-rubric @<工程>/highlight-rubric.txt $ gtrk matrix lay --project "<工程目录>" --arrange-estimate-only --json # 停在计价确认之前：零云端调用、工程文件零改动 $ gtrk transcript "<原片>" --lang <zh-CN 普通话 | zh-HK 粤语 | en-US | ja-JP …> --json -o "<工程目录>/transcript/<片名>-transcript.md" gtrk matrix material "<情绪+地理文化检索词>" --scope audio --top-k 5 --diversity --json g $ gtrk patch move --project <dir> --clip <clip_id> --to 5.0 gtrk patch trim --project <dir> --clip <clip_id> --out -1s
llm:baseline ok · 31.1s

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

$ pwd; ls -la; echo "---SKILL---"; ls -la ./skill 2>/dev/null $ which gtrk; gtrk --version 2>&1 | head -5; echo "---"; ls ~/.gitruck 2>/dev/null $ cat README.md; echo "---PKG---"; cat package.json; echo "---ENV---"; cat .env; echo "---SRC---"; ls -la src; echo "---GITIGNORE---"; cat .gitignore $ ls -la skill/references; echo "---META---"; cat skill/_meta.json; echo "---CARD---"; cat skill/skill-card.md $ cat src/index.js; echo "---GIT LOG---"; git log --oneline -10 2>&1; echo "---STATUS---"; git status --short 2>&1 | head -20 $ which node npm ffmpeg ffprobe 2>&1; echo "---"; node --version 2>&1; npm --version 2>&1; echo "---NET---"; timeout 8 curl -sS -o /dev/null -w "%{http_code}\n" https://registry.npmjs.org/@gitruck/cli 2 $ cd /var/tmp && timeout 180 npm install -g @gitruck/cli 2>&1 | tail -20; echo "EXIT:$?"; which gtrk; gtrk --version 2>&1 | head -3 $ timeout 20 curl -sS https://registry.npmjs.org/@gitruck%2Fcli 2>&1 | head -c 600; echo; echo "---SEARCH---"; timeout 20 curl -sS "https://registry.npmjs.org/-/v1/search?text=gitruck&size=10" 2>&1 | he model said: I'll start by looking at the project directory and the skill's supporting files.

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.