Verdict

No malicious behavior observed

We ran it 8 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, SCAVIO_API_KEY set and cloud credentials present. It contacted api.scavio.dev and registry.npmjs.org. It did not touch the fake credentials we planted, and nothing it sent carried them.

4 findings. Scanned 26 Oct 2026 by detonator 0.5.1.

Target: kroger-grocery-data
Source: clawhub 1.0.0
SHA-256: cab6bd7755fdf9fb
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 8 runs

Package kroger-grocery-data 3 files · agent skill
Install No install scripts of its ownOnly the package manager ran.
Runs as curl -X POST https://api.scavio.dev/api/v1/kroger/search -H Authorization: Bearer curl -X POST https://api.scavio.dev/api/v1/kroger/search -H Authorization: Bearer HTENVM2Wcurl -X POST https://api.scavio.dev/api/v1/kroger/search -H Authorization: Bearer HTENVAM1curl -X POST https://api.scavio.dev/api/v1/kroger/search -H Authorization: Bearer HTENV0Q4
What it reached
Network
- api.scavio.dev 4 connections, 854 B sent
- registry.npmjs.org 44 connections, 15.4 KB sent · during install
Credentials
None of the planted fake keys were touched.

~/.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 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:baseline

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.

F02 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.

F03 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.

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.

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/kroger/search ...
- runcurl -X POST https://api.scavio.dev/api/v1/kroger/search -H Authorization: Bearer
  - netapi.scavio.dev:443 sent 199 B
runbash -c pip install scavio==0.18.0
- runpip install scavio==0.18.0
runbash -c npm install [email protected]
- runnpm install [email protected]
  - runnode /usr/bin/npm install [email protected]
    - secretread ~/.npmrc (its own config)
    - netregistry.npmjs.org:443 sent 436 B
    - netregistry.npmjs.org:443 sent 388 B
    - netregistry.npmjs.org:443 sent 378 B
    - netregistry.npmjs.org:443 sent 386 B ×2
    - netDNS lookups for npmjs.org, scavio.dev 4 queries

Exploration log

8 runs

obedient:baseline ok · 33.1s

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/kroger/search \ -H "Authorization: Bearer $SCAVIO_API_KEY" \ -H "Content-Type: application/json" \ -d '{"query": "organic eggs"}' $ pip install scavio==0.18.0 $ npm install [email protected]
obedient:guided:ANDROID_DATA,APPENGINE_RUNTIME,CURL_CA_BUNDLE,DEB_PYTHON_INSTALL_LAYOUT… ok · 25.9s

new behavior: write:~/.npm/_cacache/content-v2/sha512/9e/b3/*, write:~/.npm/_cacache/tmp/15a2d967, write:~/.npm/_cacache/tmp/160b445c, write:~/.npm/_cacache/tmp/5f03dff5

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

new behavior: write:~/.npm/_cacache/content-v2/sha512/2c/5d/*, write:~/.npm/_cacache/tmp/18dfcc4b, write:~/.npm/_cacache/tmp/8c6444c1, write:~/.npm/_cacache/tmp/b4ddc999

$ export SCAVIO_API_KEY=sk_live_your_key $ Authorization: Bearer $SCAVIO_API_KEY $ curl -X POST https://api.scavio.dev/api/v1/kroger/search \ -H "Authorization: Bearer $SCAVIO_API_KEY" \ -H "Content-Type: application/json" \ -d '{"query": "organic eggs"}' $ pip install scavio==0.18.0 $ npm install [email protected]
obedient:declared-env ok · 19.7s

new behavior: handover:config-secret-egress, write:~/.npm/_cacache/content-v2/sha512/24/76/*, write:~/.npm/_cacache/tmp/4cc6fd89, write:~/.npm/_cacache/tmp/50adb2c1

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

new behavior: write:~/.npm/_cacache/content-v2/sha512/39/c6/*, write:~/.npm/_cacache/tmp/*, write:~/.npm/_cacache/tmp/705f7de4, write:~/.npm/_cacache/tmp/a2f58886

$ export SCAVIO_API_KEY=sk_live_your_key $ Authorization: Bearer $SCAVIO_API_KEY $ curl -X POST https://api.scavio.dev/api/v1/kroger/search \ -H "Authorization: Bearer $SCAVIO_API_KEY" \ -H "Content-Type: application/json" \ -d '{"query": "organic eggs"}' $ pip install scavio==0.18.0 $ npm install [email protected]
obedient:guided:SCAVIO_API_KEY ok · 19.7s

new behavior: write:~/.npm/_cacache/content-v2/sha512/17/51/*, write:~/.npm/_cacache/tmp/45eacd56, write:~/.npm/_cacache/tmp/486e2be0, write:~/.npm/_cacache/tmp/9abec92e

$ export SCAVIO_API_KEY=sk_live_your_key $ Authorization: Bearer $SCAVIO_API_KEY $ curl -X POST https://api.scavio.dev/api/v1/kroger/search \ -H "Authorization: Bearer $SCAVIO_API_KEY" \ -H "Content-Type: application/json" \ -d '{"query": "organic eggs"}' $ pip install scavio==0.18.0 $ npm install [email protected]
obedient:cloud-creds ok · 19.8s

new behavior: write:~/.npm/_cacache/content-v2/sha512/3e/5e/*, write:~/.npm/_cacache/tmp/*f, write:~/.npm/_cacache/tmp/1a45f316, write:~/.npm/_cacache/tmp/a*e

$ export SCAVIO_API_KEY=sk_live_your_key $ Authorization: Bearer $SCAVIO_API_KEY $ curl -X POST https://api.scavio.dev/api/v1/kroger/search \ -H "Authorization: Bearer $SCAVIO_API_KEY" \ -H "Content-Type: application/json" \ -d '{"query": "organic eggs"}' $ pip install scavio==0.18.0 $ npm install [email protected]
obedient:guided:ANDROID_DATA,APPENGINE_RUNTIME,AWS_ACCESS_KEY_ID,AWS_REGION… ok · 21.7s

new behavior: write:~/.npm/_cacache/content-v2/sha512/ac/cf/*, write:~/.npm/_cacache/tmp/12ffc06b, write:~/.npm/_cacache/tmp/50fa5f7e, write:~/.npm/_cacache/tmp/779e4726

$ export SCAVIO_API_KEY=sk_live_your_key $ Authorization: Bearer $SCAVIO_API_KEY $ curl -X POST https://api.scavio.dev/api/v1/kroger/search \ -H "Authorization: Bearer $SCAVIO_API_KEY" \ -H "Content-Type: application/json" \ -d '{"query": "organic eggs"}' $ pip install scavio==0.18.0 $ npm install [email protected]

obedient: run budget spent; llm: run budget spent

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.