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

Verdict

No malicious behavior observed

We ran it 7 times, with a normal setup, ANDROID_DATA and APPENGINE_RUNTIME and CURL_CA_BUNDLE and DEB_PYTHON_INSTALL_LAYOUT… set, the environment variables it says it needs and SCAVIO_API_KEY set. It contacted api.scavio.dev and registry.npmjs.org. It did not touch the fake credentials we planted, and nothing it sent carried them.

5 findings. Scanned 26 Oct 2026 by detonator 0.5.1.

Target
decathlon-product-data
Source
clawhub 1.0.0
SHA-256
679dd0069616f908
Files
3
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 7 runs
  1. Package decathlon-product-data 3 files · agent skill
  2. Install No install scripts of its ownOnly the package manager ran.
  3. Runs as curl -X POST https://api.scavio.dev/api/v1/decathlon/search -H Authorization: Bearer curl -X POST https://api.scavio.dev/api/v1/decathlon/search -H Authorization: Bearer HTENVls -acat .env An AI agent also used it 1 time.
  4. What it reached
    Network
    • api.scavio.dev 3 connections, 718 B sent
    • registry.npmjs.org 4 connections, 436 B 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

Network destinations contacted

Confidence
Info The package connected to these hosts.
Observed in
obedient: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.scavio.dev
registry.npmjs.org

Remediation

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

F02 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
obedient: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)

Remediation

No action needed.

F03 Low

Used the planted login with its own service (registry.npmjs.org)

Confidence
Info A planted login went to the service it belongs to, as normal authentication (npm sending its token to registry.npmjs.org while installing).
Observed in
obedient:guided:ANDROID_DATA,APPENGINE_RUNTIME,CURL_CA_BUNDLE,DEB_PYTHON_INSTALL_LAYOUT…

Description

A planted login was sent to the service it belongs to, only as the Authorization header of ordinary requests: for example npm sending the ~/.npmrc token to registry.npmjs.org while installing dependencies.

Impact

None in itself: this is how the package manager authenticates. Publishing, unpublishing or creating tokens with it would be reported as exfiltration.

Evidence

~/.npmrc (npm) sent only as the login header of ordinary requests (no publish)

Remediation

No action needed.

F04 Low

The fake credential we configured was sent to its API (expected)

Confidence
Info The fake API key we configured to start the server was sent to its own service.
Observed in
obedient:declared-env

Description

A fake credential Detonator configured to start the server was sent to its own API.

Impact

Expected for servers that wrap an online service.

Evidence

$SCAVIO_API_KEY: sent to api.scavio.dev

Remediation

Confirm the host is the service the key belongs to.

F05 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 obedient: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.

Show process tree
  • runbash -c export SCAVIO_API_KEY=sk_live_your_key
  • runbash -c Authorization: Bearer $SCAVIO_API_KEY
  • runbash -c curl -X POST https://api.scavio.dev/api/v1/decathlon/sear...
    • runcurl -X POST https://api.scavio.dev/api/v1/decathlon/search -H Authorization: Bearer
      • netapi.scavio.dev:443 sent 220 B
      • netDNS lookups for npmjs.org, scavio.dev 4 queries
  • runbash -c pip install scavio==0.18.0
    • runpip install scavio==0.18.0
  • runbash -c npm install [email protected]

Exploration log

7 runs
  1. obedient:baseline ok · 44.3s

    new behavior: dns:api.scavio.dev, dns:registry.npmjs.org, exec:curl, ownread:~/.npmrc

    $ export SCAVIO_API_KEY=sk_live_your_key $ Authorization: Bearer $SCAVIO_API_KEY $ curl -X POST https://api.scavio.dev/api/v1/decathlon/search \ -H "Authorization: Bearer $SCAVIO_API_KEY" \ -H "Content-Type: application/json" \ -d '{"query": "running shoes", "country": "fr"}' $ pip install scavio==0.18.0 $ npm install [email protected]
  2. obedient:guided:ANDROID_DATA,APPENGINE_RUNTIME,CURL_CA_BUNDLE,DEB_PYTHON_INSTALL_LAYOUT… ok · 38.2s

    no new behavior

    $ export SCAVIO_API_KEY=sk_live_your_key $ Authorization: Bearer $SCAVIO_API_KEY $ curl -X POST https://api.scavio.dev/api/v1/decathlon/search \ -H "Authorization: Bearer $SCAVIO_API_KEY" \ -H "Content-Type: application/json" \ -d '{"query": "running shoes", "country": "fr"}' $ pip install scavio==0.18.0 $ npm install [email protected]
  3. obedient:guided:ANDROID_DATA,APPENGINE_RUNTIME,CURL_CA_BUNDLE,DEB_PYTHON_INSTALL_LAYOUT… ok · 36.6s

    new behavior: write:~/.npm/_update-notifier-last-checked

    $ export SCAVIO_API_KEY=sk_live_your_key $ Authorization: Bearer $SCAVIO_API_KEY $ curl -X POST https://api.scavio.dev/api/v1/decathlon/search \ -H "Authorization: Bearer $SCAVIO_API_KEY" \ -H "Content-Type: application/json" \ -d '{"query": "running shoes", "country": "fr"}' $ pip install scavio==0.18.0 $ npm install [email protected]
  4. obedient:declared-env ok · 36.5s

    new behavior: handover:config-secret-egress

    $ export SCAVIO_API_KEY=sk_live_your_key $ Authorization: Bearer $SCAVIO_API_KEY $ curl -X POST https://api.scavio.dev/api/v1/decathlon/search \ -H "Authorization: Bearer $SCAVIO_API_KEY" \ -H "Content-Type: application/json" \ -d '{"query": "running shoes", "country": "fr"}' $ pip install scavio==0.18.0 $ npm install [email protected]
  5. obedient:guided:ANDROID_DATA,APPENGINE_RUNTIME,CURL_CA_BUNDLE,DEB_PYTHON_INSTALL_LAYOUT… ok · 38.8s

    no new behavior

    $ export SCAVIO_API_KEY=sk_live_your_key $ Authorization: Bearer $SCAVIO_API_KEY $ curl -X POST https://api.scavio.dev/api/v1/decathlon/search \ -H "Authorization: Bearer $SCAVIO_API_KEY" \ -H "Content-Type: application/json" \ -d '{"query": "running shoes", "country": "fr"}' $ pip install scavio==0.18.0 $ npm install [email protected]
  6. obedient:guided:SCAVIO_API_KEY ok · 41.2s

    no new behavior

    $ export SCAVIO_API_KEY=sk_live_your_key $ Authorization: Bearer $SCAVIO_API_KEY $ curl -X POST https://api.scavio.dev/api/v1/decathlon/search \ -H "Authorization: Bearer $SCAVIO_API_KEY" \ -H "Content-Type: application/json" \ -d '{"query": "running shoes", "country": "fr"}' $ pip install scavio==0.18.0 $ npm install [email protected]
  7. llm:baseline ok · 9.4s

    new behavior: ownread:./.env · 4 model steps, 3 commands

    $ echo "KEY set: ${SCAVIO_API_KEY:+yes}"; echo "len: ${#SCAVIO_API_KEY}"; ls -a $ cat .env 2>/dev/null | sed 's/=.*/=<redacted>/'; echo "---"; cat package.json; echo "---"; ls -R src | head -50; echo "---"; cat README.md | head -40 $ env | grep -i -E 'scavio|decathlon' || echo "no scavio env vars"; ls ~ 2>/dev/null | head model said: I can't run the skill's endpoints yet: `SCAVIO_API_KEY` is not set in this environment (I checked the shell env and the project `.env`, which only holds `OPENAI_API_KEY` and `DATABASE_URL` — I did not read or print their values). **What the skill does (ready to use once a key exists):** | Endpoint | Cost | Returns | |---|---|---| | `POST https://api.scavio.dev/api/v1/decathlon/search` | 2 credit

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.