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 and 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: firecrawl-crawl
Source: clawhub 1.0.0
SHA-256: 78a0dd0a051cff9a
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

Package firecrawl-crawl 3 files · agent skill
Install No install stepFiles were copied in as they are.
Runs as ls -lals -la skillwhich firecrawl npxhead -5 An AI agent also used it 1 time.
What it reached
Network
- api.firecrawl.dev 1 connection, 80 B sent
- registry.npmjs.org 9 connections, 3.6 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

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 package.json .gitignore; echo ---; ls src; ...
- runsed s/=.*/=<redacted>/ .env
  - secretread ./.env
runbash -c grep -c FIRECRAWL .env; env | grep -i firecrawl | sed 's/...
- rungrep -c FIRECRAWL .env
  - secretread ./.env

View full process tree

runbash -c ls -la; ls -la skill 2>/dev/null; which firecrawl npx; fi...
- runls -la
- runls -la skill
- runwhich firecrawl npx
- runhead -5
runbash -c cat README.md package.json .gitignore; echo ---; ls src; ...
- runsed s/=.*/=<redacted>/ .env
  - secretread ./.env
- runcat README.md package.json .gitignore
- runls src
- runcat skill/_meta.json
runbash -c grep -c FIRECRAWL .env; env | grep -i firecrawl | sed 's/...
- rungrep -c FIRECRAWL .env
  - secretread ./.env
- rungrep -i firecrawl
- runenv
- runsed s/=.*/=<set>/
- runtail -2
- runnpx --no-install firecrawl --version
  - runnode /usr/bin/npx --no-install firecrawl --version
    - secretread ~/.npmrc (its own config)
    - netregistry.npmjs.org:443 sent 433 B
    - netregistry.npmjs.org:443 sent 445 B
runbash -c timeout 60 npm view firecrawl version 2>&1 | tail -3; tim...
- runtail -3
- 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
- runtimeout 30 curl -sS -o /dev/null
  - runcurl -sS -o /dev/null -w %{http_code}\n
    - netapi.firecrawl.dev:443 sent 80 B
runbash -c timeout 120 npx -y firecrawl-cli --version 2>&1 | tail -3...
- runtimeout 120 npx -y firecrawl-cli --version
  - runnpx -y firecrawl-cli --version
    - runnode /usr/bin/npx -y firecrawl-cli --version
      - secretread ~/.npmrc (its own config)
      - netregistry.npmjs.org:443 sent 453 B
- runtail -3
runbash -c timeout 60 npm view firecrawl-cli version 2>&1 | tail -3;...
- runtail -3 ×2
- runtimeout 60 npm view firecrawl-cli version
  - runnpm view firecrawl-cli version
    - runnode /usr/bin/npm view firecrawl-cli version
      - secretread ~/.npmrc (its own config)
      - netregistry.npmjs.org:443 sent 397 B
- 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
runbash -c timeout 60 npm view firecrawl-cli version; echo "exit=$?"...
- runtimeout 60 npm view firecrawl-cli version
  - runnpm view firecrawl-cli version
    - runnode /usr/bin/npm view firecrawl-cli version
      - secretread ~/.npmrc (its own config)
      - netregistry.npmjs.org:443 sent 397 B
- 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
runbash -c timeout 60 npm view firecrawl --json 2>&1 | head -20; ech...
- runhead -20
- runtimeout 60 npm view firecrawl --json
  - runnpm view firecrawl --json
    - runnode /usr/bin/npm view firecrawl --json
      - secretread ~/.npmrc (its own config)
      - netregistry.npmjs.org:443 sent 389 B
      - netDNS lookups for firecrawl.dev, npmjs.org 18 queries
- runtimeout 60 npm config get registry
  - runnpm config get registry
    - runnode /usr/bin/npm config get registry
      - secretread ~/.npmrc (its own config)

Exploration log

4 runs

obedient:baseline ok · 0.8s

no new behavior

$ firecrawl crawl "<url>" --include-paths /docs --limit 50 --wait -o .firecrawl/crawl.json firecrawl crawl "<url>" --max-depth 3 --wait --progress -o .firecrawl/crawl.json firecrawl crawl <job-id>
obedient:ci-github ok · 0.5s

no new behavior

$ firecrawl crawl "<url>" --include-paths /docs --limit 50 --wait -o .firecrawl/crawl.json firecrawl crawl "<url>" --max-depth 3 --wait --progress -o .firecrawl/crawl.json firecrawl crawl <job-id>
obedient:cloud-creds ok · 0.6s

no new behavior

$ firecrawl crawl "<url>" --include-paths /docs --limit 50 --wait -o .firecrawl/crawl.json firecrawl crawl "<url>" --max-depth 3 --wait --progress -o .firecrawl/crawl.json firecrawl crawl <job-id>
llm:baseline ok · 97.2s

new behavior: dns:api.firecrawl.dev, dns:registry.npmjs.org, exec:curl, ownread:./.env · 8 model steps, 8 commands

$ ls -la; ls -la skill 2>/dev/null; which firecrawl npx; firecrawl --version 2>&1 | head -5 $ cat README.md package.json .gitignore; echo ---; ls src; echo ---; sed 's/=.*/=<redacted>/' .env; echo ---; cat skill/_meta.json $ grep -c FIRECRAWL .env; env | grep -i firecrawl | sed 's/=.*/=<set>/'; npx --no-install firecrawl --version 2>&1 | tail -2 $ timeout 60 npm view firecrawl version 2>&1 | tail -3; timeout 30 curl -sS -o /dev/null -w '%{http_code}\n' https://api.firecrawl.dev 2>&1 $ timeout 120 npx -y firecrawl-cli --version 2>&1 | tail -3; echo "exit=$?" $ timeout 60 npm view firecrawl-cli version 2>&1 | tail -3; timeout 60 npm view @mendable/firecrawl-cli version 2>&1 | tail -3 $ timeout 60 npm view firecrawl-cli version; echo "exit=$?"; timeout 60 npm view firecrawl version; echo "exit=$?" $ timeout 60 npm view firecrawl --json 2>&1 | head -20; echo "exit=$?"; timeout 60 npm config get registry model said: The `firecrawl` CLI isn't installed. Let me check the project context and whether the API key is available.

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.