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 clawhub.ai, 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-vlog-docu
Source: clawhub 1.3.9
SHA-256: 88010243a292c072
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-vlog-docu 3 files · agent skill
Install No install stepFiles were copied in as they are.
Runs as ls -lals -la skillhead -50which gtrk An AI agent also used it 1 time.
What it reached
Network
- clawhub.ai 1 connection, 102 B sent
- github.com 1 connection, 84 B sent
- registry.npmjs.org 6 connections, 1.5 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

clawhub.ai

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 "---"; cat package.json; echo "---"; ...
- 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; gtrk --version 2>&1 | head -5; echo "---"; gt...
- runwhich gtrk
- runhead -5
- runhead -60
runbash -c cat README.md; echo "---"; cat package.json; echo "---"; ...
- runcat .env
  - secretread ./.env
- runcat README.md
- runcat package.json
- runls -la src
- runcat skill/_meta.json
- runcat skill/skill-card.md
runbash -c cd /var/tmp/detonator-runs/fbc0606c91a84455acc3a490d004a4...
- rungit log --oneline
- runhead -20 ×2
- runfind / -name *.mp4 -o -name
- rungrep -v proc
runbash -c cd /var/tmp/detonator-runs/fbc0606c91a84455acc3a490d004a4...
- runcat src/index.js
- runls -la ~/.gitruck
- runnode --version
- runnpm --version
  - runnode /usr/bin/npm --version
    - secretread ~/.npmrc (its own config)
- runtail -3
- runtimeout 8 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 /var/tmp/detonator-runs/fbc0606c91a84455acc3a490d004a4...
- runtail -5
- runtimeout 20 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 397 B
      - netregistry.npmjs.org:443 sent 433 B
- runtimeout 5 curl -sS -o /dev/null
  - runcurl -sS -o /dev/null -w %{http_code}\n
    - netregistry.npmjs.org:443 sent 81 B
runbash -c cd /var/tmp/detonator-runs/fbc0606c91a84455acc3a490d004a4...
- runtimeout 30 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 600
- runhead -20
- runtimeout 20 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
runbash -c cd /var/tmp/detonator-runs/fbc0606c91a84455acc3a490d004a4...
- runtimeout 20 curl -sS -o /dev/null
  - runcurl -sS -o /dev/null -w npmjs:%{http_code}\n
    - netregistry.npmjs.org:443 sent 88 B
- runtimeout 20 curl -sS -o /dev/null
  - runcurl -sS -o /dev/null -w github:%{http_code}\n
    - netgithub.com:443 sent 84 B
- runtimeout 20 curl -sS -o /dev/null
  - runcurl -sS -o /dev/null -w clawhub:%{http_code}\n
    - netclawhub.ai:443 sent 102 B
    - netDNS lookups for clawhub.ai, github.com, npmjs.org 16 queries
- runenv
- rungrep -i -E gtrk|gitruck|api_base

Exploration log

4 runs

obedient:baseline ok · 3.1s

no new behavior

$ gtrk tool video_highlight "<本地视频>" --out "<工程目录>/highlight/<素材名>" --json $ ① 理解 transcript 抽听定档 + matrix index/describe 建素材索引 ② 立神 ★【多轮对话·必问】与创作者访谈找出那根线，问够为止（§3.2） ③ 选材串珠按「神」挑素材、定幕结构（服务于神，不是按时间流水排） ④ 写稿只写定调层旁白（§三）→ 稿 + 标题 + HashTag ⑤ 检查点① 【必停】神 · $ 到场定位（口播或旁白一句）→ 背景科普（旁白）→ 现场体验（同期声，让开）→ 攻略数字（旁白/字卡）→ 转场（车程字卡） $ gtrk transcript "<代表素材>" --lang zh-CN --json gtrk matrix index --dirs "<素材夹>" --json # 建本地索引（素材本体不上传） gtrk matrix material "<情绪+题材检索词>" --scope audio --top-k 5 --diversity --json # BGM 候选 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.6s

no new behavior

$ gtrk tool video_highlight "<本地视频>" --out "<工程目录>/highlight/<素材名>" --json $ ① 理解 transcript 抽听定档 + matrix index/describe 建素材索引 ② 立神 ★【多轮对话·必问】与创作者访谈找出那根线，问够为止（§3.2） ③ 选材串珠按「神」挑素材、定幕结构（服务于神，不是按时间流水排） ④ 写稿只写定调层旁白（§三）→ 稿 + 标题 + HashTag ⑤ 检查点① 【必停】神 · $ 到场定位（口播或旁白一句）→ 背景科普（旁白）→ 现场体验（同期声，让开）→ 攻略数字（旁白/字卡）→ 转场（车程字卡） $ gtrk transcript "<代表素材>" --lang zh-CN --json gtrk matrix index --dirs "<素材夹>" --json # 建本地索引（素材本体不上传） gtrk matrix material "<情绪+题材检索词>" --scope audio --top-k 5 --diversity --json # BGM 候选 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 · 4.2s

no new behavior

$ gtrk tool video_highlight "<本地视频>" --out "<工程目录>/highlight/<素材名>" --json $ ① 理解 transcript 抽听定档 + matrix index/describe 建素材索引 ② 立神 ★【多轮对话·必问】与创作者访谈找出那根线，问够为止（§3.2） ③ 选材串珠按「神」挑素材、定幕结构（服务于神，不是按时间流水排） ④ 写稿只写定调层旁白（§三）→ 稿 + 标题 + HashTag ⑤ 检查点① 【必停】神 · $ 到场定位（口播或旁白一句）→ 背景科普（旁白）→ 现场体验（同期声，让开）→ 攻略数字（旁白/字卡）→ 转场（车程字卡） $ gtrk transcript "<代表素材>" --lang zh-CN --json gtrk matrix index --dirs "<素材夹>" --json # 建本地索引（素材本体不上传） gtrk matrix material "<情绪+题材检索词>" --scope audio --top-k 5 --diversity --json # BGM 候选 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 · 73.4s

new behavior: dns:clawhub.ai, dns:github.com, dns:registry.npmjs.org, exec:curl · token budget reached

$ pwd; ls -la; echo "---"; ls -la skill 2>/dev/null | head -50 $ which gtrk; gtrk --version 2>&1 | head -5; echo "---"; gtrk --help 2>&1 | head -60 $ cat README.md; echo "---"; cat package.json; echo "---"; cat .env; echo "---"; ls -la src; echo "---"; cat skill/_meta.json; echo "---"; cat skill/skill-card.md $ cd /var/tmp/detonator-runs/fbc0606c91a84455acc3a490d004a4dd/work && git log --oneline | head -20; echo "---"; find / -name "*.mp4" -o -name "*.mov" -o -name "*.MP4" 2>/dev/null | grep -v proc | head - $ cd /var/tmp/detonator-runs/fbc0606c91a84455acc3a490d004a4dd/work && cat src/index.js; echo "---"; ls -la ~/.gitruck 2>/dev/null; echo "--- node/npm"; node --version; npm --version; echo "--- net"; tim $ cd /var/tmp/detonator-runs/fbc0606c91a84455acc3a490d004a4dd/work && timeout 20 npm view @gitruck/cli version 2>&1 | tail -5; echo "exit=$?"; echo "--- ping"; timeout 5 curl -sS -o /dev/null -w "%{http $ cd /var/tmp/detonator-runs/fbc0606c91a84455acc3a490d004a4dd/work && timeout 30 curl -sS https://registry.npmjs.org/@gitruck%2Fcli 2>&1 | head -c 600; echo; echo "---"; timeout 20 npm view @gitruck/cli $ cd /var/tmp/detonator-runs/fbc0606c91a84455acc3a490d004a4dd/work && timeout 20 curl -sS -o /dev/null -w "npmjs:%{http_code}\n" https://registry.npmjs.org/express; timeout 20 curl -sS -o /dev/null -w " 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.