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 27 Oct 2026 by detonator 0.5.1.

Target
mobile-flutter
Source
clawhub 1.0.1
SHA-256
85c62fa01e8a3d2f
Files
7
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 1 run
  1. Package mobile-flutter 7 files · agent skill
  2. Install No install stepFiles were copied in as they are.
  3. Runs as ls -lafind . -maxdepth 3 -name pubspec.yamlhead -20ls -la ./skill An AI agent also used it 1 time.
  4. What it reached
    Network

    No connections.

    Credentials
    • ./.envread
    Files written
    • ./.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

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.

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 .gitignore; echo "--- ENV ---"...
    • runcat .env
      • secretread ./.env
View full process tree
  • runbash -c pwd && ls -la && find . -maxdepth 3 -name "pubspec.yaml" ...
    • runls -la
    • runfind . -maxdepth 3 -name pubspec.yaml
    • runhead -20
  • runbash -c ls -la ./skill 2>/dev/null && find ./skill -type f | head...
    • runls -la ./skill
    • runfind ./skill -type f
    • runhead -50
  • runbash -c cat README.md package.json .gitignore; echo "--- ENV ---"...
    • runcat .env
      • secretread ./.env
    • runcat README.md package.json .gitignore
    • runls -la src
    • runcat src/index.js
  • runbash -c cd /var/tmp/detonator-runs/b1df28fac15246c2b8f68515e5dc22...
    • rungit log --oneline -10
    • runcat skill/_meta.json skill/skill-card.md
  • runbash -c cd /var/tmp/detonator-runs/b1df28fac15246c2b8f68515e5dc22...
    • runwhich flutter dart node npm
    • rungit status --short
      • filewrote ./.git/index.lock
    • runwc -l skill/references/performance.md skill/references/platform-channels.md skill/references/state-management.md skill/references/testing.md
  • runbash -c cd /var/tmp/detonator-runs/b1df28fac15246c2b8f68515e5dc22...
    • runsed -n 1,80p skill/references/state-management.md

Exploration log

1 run
  1. llm:baseline ok · 16.9s

    new behavior: ownread:./.env, write:./.git/index, write:./.git/index.lock · 5 model steps, 6 commands

    $ pwd && ls -la && find . -maxdepth 3 -name "pubspec.yaml" -o -maxdepth 3 -name "analysis_options.yaml" | head -20 $ ls -la ./skill 2>/dev/null && find ./skill -type f | head -50 $ cat README.md package.json .gitignore; echo "--- ENV ---"; cat .env; echo "--- SRC ---"; ls -la src; echo; for f in src/*; do echo "=== $f ==="; cat "$f"; done $ cd /var/tmp/detonator-runs/b1df28fac15246c2b8f68515e5dc22f5/work && git log --oneline -10 && cat skill/_meta.json skill/skill-card.md $ cd /var/tmp/detonator-runs/b1df28fac15246c2b8f68515e5dc22f5/work && which flutter dart node npm 2>&1; echo "---"; git status --short; echo "--- refs ---"; wc -l skill/references/*.md $ cd /var/tmp/detonator-runs/b1df28fac15246c2b8f68515e5dc22f5/work && sed -n 1,80p skill/references/state-management.md model said: I inspected the project before writing anything. Here's what I found and what I did. ## What's in the project `payments-api` is a **Node.js/Express service** (`package.json`, `src/index.js` with a single `/health` route). There is **no Flutter or Dart project here**: no `pubspec.yaml`, no `analysis_options.yaml`, no `lib/`, no `test/`, and neither `flutter` nor `dart` is installed on this machin

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.