Verdict

No malicious behavior observed

We ran it 7 times, with a normal setup, LC_MESSAGES set, docs:check and everything. 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: qa-suite
Source: clawhub 1.0.0
SHA-256: 34631c787a34d69f
Files: 17

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 7 runs

Package qa-suite 17 files · agent skill
Install No install stepFiles were copied in as they are.
Runs as python3 <skill>/scripts/validate_qa_gate.pypython3 <skill>/scripts/validate_qa_gate.py checkls -lals -R ./skill An AI agent also used it 1 time.
What it reached
Network
- registry.npmjs.org 1 connection, 433 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 cd /var/tmp/detonator-runs/bf20bf25199245469f572ffd8d3311...
- runcat .env
  - secretread ./.env

View full process tree

runbash -c cd /home/user 2>/dev/null; pwd; ls -la; echo "---SKILL---...
- runls -la
- runls -R ./skill
- runhead -50
runbash -c cd /home/user 2>/dev/null; find . -maxdepth 2 -name "pack...
- runfind . -maxdepth 2 -name package.json
runbash -c cd /var/tmp/detonator-runs/bf20bf25199245469f572ffd8d3311...
- runcat .env
  - secretread ./.env
- runcat package.json
- runcat README.md
- runcat .gitignore
- runls -la src
- runhead -20
- rungit log --oneline
runbash -c cd /var/tmp/detonator-runs/bf20bf25199245469f572ffd8d3311...
- runcat skill/references/environment-inspection.md
runbash -c cd /var/tmp/detonator-runs/bf20bf25199245469f572ffd8d3311...
- runcat src/index.js
- runls -la scripts
- runls -la .github
- runnode --version
- runnpm --version
  - runnode /usr/bin/npm --version
    - secretread ~/.npmrc (its own config)
- runls node_modules
- runhead -5
runbash -c cd /var/tmp/detonator-runs/bf20bf25199245469f572ffd8d3311...
- runcat skill/references/test-types.md
- runcat skill/references/no-environment.md
runbash -c cd /var/tmp/detonator-runs/bf20bf25199245469f572ffd8d3311...
- runcat skill/references/integration-test-execution.md
runbash -c cd /var/tmp/detonator-runs/bf20bf25199245469f572ffd8d3311...
- runcat skill/references/e2e-test-execution.md
runbash -c cd /var/tmp/detonator-runs/bf20bf25199245469f572ffd8d3311...
- runsed -n 1,120p skill/references/integration-test-execution.md
runbash -c cd /var/tmp/detonator-runs/bf20bf25199245469f572ffd8d3311...
- runsed -n 1,120p skill/references/e2e-test-execution.md
- runcat skill/scripts/validate_qa_gate.py
runbash -c cd /var/tmp/detonator-runs/bf20bf25199245469f572ffd8d3311...
- runsed -n 1,140p skill/scripts/validate_qa_gate.py
runbash -c cd /var/tmp/detonator-runs/bf20bf25199245469f572ffd8d3311...
- runsed -n 1,80p skill/references/e2e-test-execution.md
runbash -c cd /var/tmp/detonator-runs/bf20bf25199245469f572ffd8d3311...
- runsed -n 140,200p skill/scripts/validate_qa_gate.py
- runsed -n 1,60p skill/references/environment-backend.md
runbash -c cd /var/tmp/detonator-runs/bf20bf25199245469f572ffd8d3311...
- runnpm test
  - runnode /usr/bin/npm test
    - secretread ~/.npmrc (its own config)
    - netregistry.npmjs.org:443 sent 433 B
    - netDNS lookups for npmjs.org 2 queries
    - runsh -c node --test
      - runnode --test
- runtail -20
- runnpm ls --depth=0
  - runnode /usr/bin/npm ls --depth=0
    - secretread ~/.npmrc (its own config)
- runhead

Exploration log

7 runs

scripts:baseline ok · 1.3s

no new behavior
scripts:guided:LC_MESSAGES ok · 1.5s

no new behavior
scripts:docs:check ok · 1.6s

no new behavior
obedient:baseline ok · 1.3s

no new behavior

$ python3 scripts/validate_qa_gate.py check <qa_report.json> [--json] $ Unit test execution is NOT this skill's job. To write unit tests using TDD: /coding-tactics tdd To write unit tests using BDD: /coding-tactics bdd $ This skill writes and executes integration tests and E2E tests directly. - Integration tests: Step 9 (references/integration-test-execution.md) - E2E tests: Step 10 (references/e2e-test-execution.md) $ - Backend Phase: invoke /qa-suite for strategy, env setup, AND integration test execution - Frontend Phase: invoke /qa-suite for strategy, env setup, AND E2E test execution - Before E2E steps: use Ste $ - Missing: {test types or capabilities not yet implemented} - Fallback plan: {no-environment strategy if applicable} 1. Run: {setup command} 2. Unit tests: invoke /coding-tactics tdd (or /coding-tacti
obedient:guided:LC_MESSAGES ok · 0.9s

no new behavior

$ python3 scripts/validate_qa_gate.py check <qa_report.json> [--json] $ Unit test execution is NOT this skill's job. To write unit tests using TDD: /coding-tactics tdd To write unit tests using BDD: /coding-tactics bdd $ This skill writes and executes integration tests and E2E tests directly. - Integration tests: Step 9 (references/integration-test-execution.md) - E2E tests: Step 10 (references/e2e-test-execution.md) $ - Backend Phase: invoke /qa-suite for strategy, env setup, AND integration test execution - Frontend Phase: invoke /qa-suite for strategy, env setup, AND E2E test execution - Before E2E steps: use Ste $ - Missing: {test types or capabilities not yet implemented} - Fallback plan: {no-environment strategy if applicable} 1. Run: {setup command} 2. Unit tests: invoke /coding-tactics tdd (or /coding-tacti
obedient:everything ok · 1.3s

no new behavior

$ python3 scripts/validate_qa_gate.py check <qa_report.json> [--json] $ Unit test execution is NOT this skill's job. To write unit tests using TDD: /coding-tactics tdd To write unit tests using BDD: /coding-tactics bdd $ This skill writes and executes integration tests and E2E tests directly. - Integration tests: Step 9 (references/integration-test-execution.md) - E2E tests: Step 10 (references/e2e-test-execution.md) $ - Backend Phase: invoke /qa-suite for strategy, env setup, AND integration test execution - Frontend Phase: invoke /qa-suite for strategy, env setup, AND E2E test execution - Before E2E steps: use Ste $ - Missing: {test types or capabilities not yet implemented} - Fallback plan: {no-environment strategy if applicable} 1. Run: {setup command} 2. Unit tests: invoke /coding-tactics tdd (or /coding-tacti
llm:baseline ok · 41.6s

new behavior: dns:registry.npmjs.org, ownread:./.env, ownread:~/.npmrc, write:~/.npm/_logs/*-debug-0.log · token budget reached

$ cd /home/user 2>/dev/null; pwd; ls -la; echo "---SKILL---"; ls -R ./skill | head -50 $ cd /home/user 2>/dev/null; find . -maxdepth 2 -name "package.json" -o -maxdepth 2 -name "go.mod" -o -maxdepth 2 -name "requirements.txt" -o -maxdepth 2 -name "pyproject.toml" -o -maxdepth 2 -name "Car $ cd /var/tmp/detonator-runs/bf20bf25199245469f572ffd8d33115e/work; cat package.json; echo "---README---"; cat README.md; echo "---ENV---"; cat .env; echo "---GITIGNORE---"; cat .gitignore; echo "---SRC $ cd /var/tmp/detonator-runs/bf20bf25199245469f572ffd8d33115e/work; cat skill/references/environment-inspection.md $ cd /var/tmp/detonator-runs/bf20bf25199245469f572ffd8d33115e/work; cat src/index.js; echo "---"; ls -la scripts 2>/dev/null || echo "no scripts dir"; echo "---CI---"; ls -la .github 2>/dev/null || echo $ cd /var/tmp/detonator-runs/bf20bf25199245469f572ffd8d33115e/work; cat skill/references/test-types.md; echo "=====NOENV====="; cat skill/references/no-environment.md $ cd /var/tmp/detonator-runs/bf20bf25199245469f572ffd8d33115e/work; cat skill/references/integration-test-execution.md $ cd /var/tmp/detonator-runs/bf20bf25199245469f572ffd8d33115e/work; cat skill/references/e2e-test-execution.md $ cd /var/tmp/detonator-runs/bf20bf25199245469f572ffd8d33115e/work; sed -n '1,120p' skill/references/integration-test-execution.md $ cd /var/tmp/detonator-runs/bf20bf25199245469f572ffd8d33115e/work; sed -n '1,120p' skill/references/e2e-test-execution.md; echo "=====GATE====="; cat skill/scripts/validate_qa_gate.py model said: I'll start by reading the skill's contract and inspecting the project.

scripts/scripts/validate_qa_gate.py: coverage plateau (2 runs with no new behavior); 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.