Detonation LabsBehavioral security for the AI agent supply chain

Verdict

No malicious behavior observed

We ran it 4 times, with a normal setup, docs:/yahoo-finance/lookup query= and docs:/yahoo-finance/industries. It contacted api.crawlora.net and www.sec.gov. It did not touch the fake credentials we planted, and nothing it sent carried them.

2 findings. Scanned 26 Oct 2026 by detonator 0.5.1.

Target
company-fundamentals-comparison
Source
clawhub 1.0.0
SHA-256
cb7bd99447a2d866
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 4 runs
  1. Package company-fundamentals-comparison 5 files · agent skill
  2. Install No install stepFiles were copied in as they are.
  3. Runs as bash <skill>/scripts/crawlora.shbash <skill>/scripts/crawlora.sh /yahoo-finance/lookup query=bash <skill>/scripts/crawlora.sh /yahoo-finance/industriesls -la An AI agent also used it 1 time.
  4. What it reached
    Network
    • api.crawlora.net 1 connection, 110 B sent
    • www.sec.gov 1 connection, 100 B sent
    Credentials
    • ./.envread
    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

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

api.crawlora.net
www.sec.gov

Remediation

Confirm each host is expected (the package's API, its registry). Allowlist expected egress in production.

F02 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 sed -n 50,200p skill/scripts/crawlora.sh; echo ---; cat s...
    • runcat .env
      • secretread ./.env
View full process tree
  • runbash -c ls -la; ls -la skill; ls -la skill/scripts 2>/dev/null; c...
    • runls -la
    • runls -la skill
    • runls -la skill/scripts
    • runhead -5
    • runcat skill/SKILL.md
  • runbash -c cat skill/scripts/crawlora.sh 2>/dev/null | head -50
    • runcat skill/scripts/crawlora.sh
    • runhead -50
  • runbash -c sed -n 50,200p skill/scripts/crawlora.sh; echo ---; cat s...
    • runcat .env
      • secretread ./.env
    • runsed -n 50,200p skill/scripts/crawlora.sh
    • runcat skill/skill-card.md
    • runls skill/reference
    • runcat skill/_meta.json
    • runcat README.md package.json
    • runls src
    • runsed s/=.*/=<redacted>/
  • runbash -c cat skill/reference/endpoints.md; echo ---; env | grep -i...
    • runcat skill/reference/endpoints.md
    • runenv
    • runsed s/=.*/=<set>/
    • rungrep -i crawlora
  • runbash -c sed -n 1,60p skill/reference/endpoints.md
    • runsed -n 1,60p skill/reference/endpoints.md
  • runbash -c cd skill/scripts && ./crawlora.sh /yahoo-finance/lookup q...
    • runhead -c 500
  • runbash -c cd skill/scripts && bash crawlora.sh /yahoo-finance/looku...
    • runbash crawlora.sh /yahoo-finance/lookup query=NVIDIA type=equity
    • runhead -c 800
  • runbash -c cd skill/scripts && bash crawlora.sh /sec/company/search ...
    • runbash crawlora.sh /sec/company/search q=NVIDIA
    • runhead -c 300
    • rungit -C /root
    • rungit log --oneline -5
    • rungrep -v ^/proc
    • rungrep -ril crawlora / --include=*.env --include=*.json
    • runhead
  • runbash -c curl -s -o /dev/null -w '%{http_code}\n' --max-time 10 ht...
    • runcurl -s -o /dev/null -w %{http_code}\n
      • netapi.crawlora.net:443 sent 110 B
    • runcurl -s -o /dev/null -w %{http_code}\n
      • netwww.sec.gov:443 sent 100 B
      • netDNS lookups for crawlora.net, sec.gov 4 queries

Exploration log

4 runs
  1. scripts:baseline ok · 0.3s

    no new behavior

  2. scripts:docs:/yahoo-finance/lookup query= ok · 0.6s

    no new behavior

  3. scripts:docs:/yahoo-finance/industries ok · 0.5s

    no new behavior

  4. llm:baseline ok · 35.1s

    new behavior: dns:api.crawlora.net, dns:www.sec.gov, exec:curl, ownread:./.env · 8 model steps, 9 commands

    $ ls -la; ls -la skill; ls -la skill/scripts 2>/dev/null; cat skill/SKILL.md | head -5 $ cat skill/scripts/crawlora.sh 2>/dev/null | head -50 $ sed -n 50,200p skill/scripts/crawlora.sh; echo ---; cat skill/skill-card.md; echo ---; ls skill/reference; cat skill/_meta.json; echo ---; cat README.md package.json; ls src; cat .env | sed 's/=.*/=<r $ cat skill/reference/endpoints.md; echo ---; env | grep -i crawlora | sed 's/=.*/=<set>/' $ sed -n 1,60p skill/reference/endpoints.md $ cd skill/scripts && ./crawlora.sh /yahoo-finance/lookup query='NVIDIA' type=equity 2>&1 | head -c 500; echo; echo "exit=$?" $ cd skill/scripts && bash crawlora.sh /yahoo-finance/lookup query='NVIDIA' type=equity 2>&1 | head -c 800; echo; echo "exit=${PIPESTATUS[0]}" $ cd skill/scripts && bash crawlora.sh /sec/company/search q='NVIDIA' 2>&1 | head -c 300; echo; git -C /root 2>/dev/null; git log --oneline -5 2>/dev/null; grep -ril crawlora / --include=*.env --include $ curl -s -o /dev/null -w '%{http_code}\n' --max-time 10 https://api.crawlora.net/api/v1/yahoo-finance/industries; curl -s -o /dev/null -w '%{http_code}\n' --max-time 10 https://www.sec.gov/files/compan model said: I'll start by exploring the project and the skill's scripts.

scripts/scripts/crawlora.sh: 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.