Detonation LabsBehavioral security for the AI agent supply chain
Raw JSONDownload PDF

Verdict

No malicious behavior observed

We ran it 1 time, with a normal setup. It made no network connections. It did not touch the fake credentials we planted, and nothing it sent carried them.

1 finding. Scanned 26 Oct 2026 by detonator 0.5.1.

Target
ai-disruption-risk-audit
Source
clawhub 1.0.0
SHA-256
a0970631c80eba07
Files
5
RecommendationNo action needed

Nothing observed calls for action. This is evidence, not a guarantee.

batch:clawhub:2026-10-26

What this package does

observed across 1 run
  1. Package ai-disruption-risk-audit 5 files · agent skill
  2. Install No install stepFiles were copied in as they are.
  3. Runs as ls -lafind . -maxdepth 3 -type fhead -100ls -R ./skill An AI agent also used it 1 time.
  4. What it reached
    Network

    No connections.

    Credentials
    • ./.envread
    Files written
    • ./audit/ai-disruption-risk-audit.mdwritten

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

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 sed)

Remediation

No action needed. Keep long-lived secrets out of project .env files where possible.

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;...
    • runsed s/=.*/=<redacted>/ .env
      • secretread ./.env
View full process tree
  • runbash -c ls -la; echo "---"; find . -maxdepth 3 -type f -not -path...
    • runls -la
    • runfind . -maxdepth 3 -type f
    • runhead -100
  • runbash -c ls -R ./skill 2>/dev/null | head -50
    • runls -R ./skill
    • runhead -50
  • runbash -c cat README.md; echo "=== package.json"; cat package.json;...
    • runsed s/=.*/=<redacted>/ .env
      • secretread ./.env
    • runcat README.md
    • runcat package.json
    • runcat src/index.js
    • rungit log --oneline
    • runhead -20
  • runbash -c cat skill/examples/chegg-generative-ai-2023-2025.md; echo...
    • runcat skill/examples/chegg-generative-ai-2023-2025.md
    • runcat skill/references/sources.md
    • runcat skill/_meta.json
  • runbash -c head -60 skill/examples/chegg-generative-ai-2023-2025.md;...
    • runhead -60 skill/examples/chegg-generative-ai-2023-2025.md
    • runcat skill/skill-card.md
  • runbash -c mkdir -p audit && cat > audit/ai-disruption-risk-audit.md...
    • filewrote ./audit/ai-disruption-risk-audit.md
    • runmkdir -p audit
    • runcat
    • runwc -l audit/ai-disruption-risk-audit.md

Exploration log

1 run
  1. llm:baseline ok · 22.6s

    new behavior: ownread:./.env, write:./audit/ai-disruption-risk-audit.md · 5 model steps, 6 commands

    $ ls -la; echo "---"; find . -maxdepth 3 -type f -not -path "./.git/*" | head -100 $ ls -R ./skill 2>/dev/null | head -50 $ cat README.md; echo "=== package.json"; cat package.json; echo "=== src/index.js"; cat src/index.js; echo "=== .env (keys only)"; sed 's/=.*/=<redacted>/' .env; echo "=== git log"; git log --oneline | $ cat skill/examples/chegg-generative-ai-2023-2025.md; echo "=== sources"; cat skill/references/sources.md; echo "=== meta"; cat skill/_meta.json $ head -60 skill/examples/chegg-generative-ai-2023-2025.md; echo "=== card"; cat skill/skill-card.md $ mkdir -p audit && cat > audit/ai-disruption-risk-audit.md <<'EOF' # AI Disruption Risk Audit — payments-api (v2.14.3) **Status: DRAFT — NOT A CONCLUSION.** No activity has been tested against AI on r model said: I ran the audit against what's actually in the project and wrote the result to `audit/ai-disruption-risk-audit.md`. **What I found in the project:** `payments-api` v2.14.3 — a thin Express service (`/health` only), deps `express`/`pg`/`stripe`, and an `OPENAI_API_KEY` already in `.env`. There is **no revenue, customer, pricing, margin or activity data** anywhere in the repo. **What I produced:**

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.