Detonation LabsBehavioral security for the AI agent supply chain

Verdict

No malicious behavior observed

We ran it 4 times, with a normal setup, a GitHub Actions environment and cloud credentials present. It contacted api.firecrawl.dev, example.com and github.com and others. 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
firecrawl-interact
Source
clawhub 1.0.0
SHA-256
df79fd41a400ecdd
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
  1. Package firecrawl-interact 3 files · agent skill
  2. Install No install stepFiles were copied in as they are.
  3. Runs as ls -lals -la ./skillwhich firecrawl npx nodesed s/=.*/=<redacted>/ .env An AI agent also used it 1 time.
  4. What it reached
    Network
    • api.firecrawl.dev 3 connections, 431 B sent
    • example.com 2 connections, 148 B sent
    • github.com 1 connection, 73 B sent
    • pypi.org 1 connection, 78 B sent
    • registry.npmjs.org 7 connections, 1.9 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

api.firecrawl.dev
example.com
github.com
pypi.org
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 grep, sed)

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, npx)

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 "---"; ...
    • runsed s/=.*/=<redacted>/ .env
      • secretread ./.env
  • runbash -c env | grep -i -E 'firecrawl|browser|agent' | sed 's/=.*/=...
    • rungrep -i firecrawl .env
      • secretread ./.env
View full process tree
  • runbash -c ls -la; echo "---"; ls -la ./skill; echo "---"; which fir...
    • runls -la
    • runls -la ./skill
    • runwhich firecrawl npx node
  • runbash -c cat README.md; echo "---"; cat package.json; echo "---"; ...
    • runsed s/=.*/=<redacted>/ .env
      • secretread ./.env
    • runcat README.md
    • runcat package.json
    • runls -la src
    • runcat skill/_meta.json
    • runcat skill/skill-card.md
  • runbash -c cd /tmp && timeout 120 npx -y firecrawl --version 2>&1 | ...
    • runtimeout 120 npx -y firecrawl --version
      • runnpx -y firecrawl --version
        • runnode /usr/bin/npx -y firecrawl --version
          • secretread ~/.npmrc (its own config)
          • netregistry.npmjs.org:443 sent 433 B
          • netregistry.npmjs.org:443 sent 445 B
    • runtail -20
  • runbash -c cd /tmp && timeout 60 npm view firecrawl version 2>&1 | t...
    • runtimeout 60 npm view firecrawl version
      • runnpm view firecrawl version
        • runnode /usr/bin/npm view firecrawl version
          • secretread ~/.npmrc (its own config)
          • netregistry.npmjs.org:443 sent 389 B
    • runtail -5 ×2
    • runtimeout 60 npm view @mendable/firecrawl-cli version
      • runnpm view @mendable/firecrawl-cli version
        • runnode /usr/bin/npm view @mendable/firecrawl-cli version
          • secretread ~/.npmrc (its own config)
          • netregistry.npmjs.org:443 sent 419 B
    • runtimeout 30 curl -sS -o /dev/null
      • runcurl -sS -o /dev/null -w %{http_code}\n
        • netregistry.npmjs.org:443 sent 81 B
  • runbash -c cd /tmp && timeout 60 curl -sS https://registry.npmjs.org...
    • runtimeout 60 curl -sS https://registry.npmjs.org/firecrawl
      • runcurl -sS https://registry.npmjs.org/firecrawl
        • netregistry.npmjs.org:443 sent 90 B
    • runhead -c 300
    • runhead -c 1500
    • runtimeout 60 curl -sS https://registry.npmjs.org/-/v1/search?text=firecrawl&siz...
      • runcurl -sS https://registry.npmjs.org/-/v1/search?text=firecrawl&siz...
        • netregistry.npmjs.org:443 sent 115 B
  • runbash -c env | grep -i -E 'firecrawl|browser|agent' | sed 's/=.*/=...
    • rungrep -i firecrawl .env
      • secretread ./.env
    • rungrep -i -E firecrawl|browser|agent
    • runsed s/=.*/=<set>/ ×2
    • runenv
    • runls ~/.config
    • runls ~/.firecrawl
    • runtimeout 30 curl -sS -o /dev/null
      • runcurl -sS -o /dev/null -w %{http_code}\n
        • netapi.firecrawl.dev:443 sent 89 B
  • runbash -c cd /tmp && timeout 60 curl -sS -X POST https://api.firecr...
    • runhead -c 500 ×2
    • runtimeout 60 curl -sS -X POST
      • runcurl -sS -X POST https://api.firecrawl.dev/v1/scrape -H
        • netapi.firecrawl.dev:443 sent 171 B
    • runtimeout 60 curl -sS -X POST
      • runcurl -sS -X POST https://api.firecrawl.dev/v2/scrape -H
        • netapi.firecrawl.dev:443 sent 171 B
  • runbash -c cd /tmp && timeout 30 curl -sS -o /dev/null -w "example.c...
    • runtimeout 30 curl -sS -o /dev/null
      • runcurl -sS -o /dev/null -w example.com %{http_code}\n
        • netexample.com:443 sent 74 B
    • runtimeout 30 curl -sS -o /dev/null
      • runcurl -sS -o /dev/null -w github %{http_code}\n
        • netgithub.com:443 sent 73 B
    • runtimeout 30 curl -sS -o /dev/null
      • runcurl -sS -o /dev/null -w pypi %{http_code}\n
        • netpypi.org:443 sent 78 B
    • runtimeout 30 curl -sS https://example.com
      • runcurl -sS https://example.com
        • netexample.com:443 sent 74 B
        • netDNS lookups for example.com, firecrawl.dev, github.com, npmjs.org, pypi.org 26 queries
    • runhead -c 300

Exploration log

4 runs
  1. obedient:baseline ok · 1.1s

    no new behavior

    $ firecrawl scrape "<url>" firecrawl interact --prompt "Click the login button" firecrawl interact --prompt "Fill in the email field with [email protected]" firecrawl interact --prompt "Extract the prici $ firecrawl scrape "https://app.example.com/login" --profile my-app firecrawl interact --prompt "Fill in email with [email protected] and click login" firecrawl scrape "https://app.example.com/dashboard" $ firecrawl scrape "https://app.example.com" --profile my-app --no-save-changes
  2. obedient:ci-github ok · 0.8s

    no new behavior

    $ firecrawl scrape "<url>" firecrawl interact --prompt "Click the login button" firecrawl interact --prompt "Fill in the email field with [email protected]" firecrawl interact --prompt "Extract the prici $ firecrawl scrape "https://app.example.com/login" --profile my-app firecrawl interact --prompt "Fill in email with [email protected] and click login" firecrawl scrape "https://app.example.com/dashboard" $ firecrawl scrape "https://app.example.com" --profile my-app --no-save-changes
  3. obedient:cloud-creds ok · 1.4s

    no new behavior

    $ firecrawl scrape "<url>" firecrawl interact --prompt "Click the login button" firecrawl interact --prompt "Fill in the email field with [email protected]" firecrawl interact --prompt "Extract the prici $ firecrawl scrape "https://app.example.com/login" --profile my-app firecrawl interact --prompt "Fill in email with [email protected] and click login" firecrawl scrape "https://app.example.com/dashboard" $ firecrawl scrape "https://app.example.com" --profile my-app --no-save-changes
  4. llm:baseline ok · 49.5s

    new behavior: dns:api.firecrawl.dev, dns:example.com, dns:github.com, dns:pypi.org · 8 model steps, 8 commands

    $ ls -la; echo "---"; ls -la ./skill; echo "---"; which firecrawl npx node 2>&1 $ cat README.md; echo "---"; cat package.json; echo "---"; ls -la src; echo "---"; cat skill/_meta.json; echo "---"; cat skill/skill-card.md; echo "---"; sed 's/=.*/=<redacted>/' .env $ cd /tmp && timeout 120 npx -y firecrawl --version 2>&1 | tail -20; echo "EXIT:$?" $ cd /tmp && timeout 60 npm view firecrawl version 2>&1 | tail -5; echo "---"; timeout 60 npm view @mendable/firecrawl-cli version 2>&1 | tail -5; echo "---"; timeout 30 curl -sS -o /dev/null -w "%{http $ cd /tmp && timeout 60 curl -sS https://registry.npmjs.org/firecrawl | head -c 300; echo; echo "---"; timeout 60 curl -sS "https://registry.npmjs.org/-/v1/search?text=firecrawl&size=10" | head -c 1500 $ env | grep -i -E 'firecrawl|browser|agent' | sed 's/=.*/=<set>/'; echo "---"; grep -i firecrawl .env 2>/dev/null | sed 's/=.*/=<set>/'; echo "---"; ls ~/.config 2>/dev/null; ls ~/.firecrawl 2>/dev/nul $ cd /tmp && timeout 60 curl -sS -X POST https://api.firecrawl.dev/v1/scrape -H 'Content-Type: application/json' -d '{"url":"https://example.com"}' | head -c 500; echo; echo "---"; timeout 60 curl -sS - $ cd /tmp && timeout 30 curl -sS -o /dev/null -w "example.com %{http_code}\n" https://example.com; timeout 30 curl -sS -o /dev/null -w "github %{http_code}\n" https://github.com; timeout 30 curl -sS -o model said: The npm registry is intercepted by a proxy returning empty results, so the Firecrawl CLI can't be installed. Let me check whether a Firecrawl API key is available as an alternative path.

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.