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

Verdict

No malicious behavior observed

We ran it 1 time, with a normal setup. It contacted registry.npmjs.org. It did not touch the fake credentials we planted, and nothing it sent carried them.

3 findings. Scanned 26 Oct 2026 by detonator 0.5.1.

Target
aicut-fake-text
Source
clawhub 1.0.0
SHA-256
fb89c37729f3e0b2
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 1 run
  1. Package aicut-fake-text 5 files · agent skill
  2. Install No install stepFiles were copied in as they are.
  3. Runs as node --versionnpm --versionnode /usr/bin/npm --versionnpm i -g aicut-cli An AI agent also used it 1 time.
  4. What it reached
    Network
    • registry.npmjs.org 8 connections, 2.2 KB sent
    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
llm: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
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

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

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.

Show process tree
  • runbash -c aicut --version; echo "---"; aicut account
  • runbash -c node --version; npm --version; npm i -g aicut-cli 2>&1 | ...
    • runnode --version
    • runnpm --version
      • runnode /usr/bin/npm --version
        • secretread ~/.npmrc (its own config)
    • runnpm i -g aicut-cli
      • runnode /usr/bin/npm i -g aicut-cli
        • secretread ~/.npmrc (its own config)
        • netregistry.npmjs.org:443 sent 392 B
        • netregistry.npmjs.org:443 sent 436 B
    • runtail -20
  • runbash -c npm view aicut-cli version 2>&1 | tail -5; echo "---"; np...
    • runnpm view aicut-cli version
      • runnode /usr/bin/npm view aicut-cli version
        • secretread ~/.npmrc (its own config)
        • netregistry.npmjs.org:443 sent 389 B
    • runtail -5
    • runnpm config get registry
      • runnode /usr/bin/npm config get registry
        • secretread ~/.npmrc (its own config)
    • runtail -30
    • runcat ~/.npm/_logs/2026-10-26T19_14_33_445Z-debug-0.log ~/.npm/_logs/2026-10-26T19_14_47_056Z-debug-0.log ~/.npm/_logs/2026-10-26T19_14_55_103
  • runbash -c npm view aicut-cli 2>&1 | head -40; echo "=== dist-tags =...
    • runhead -40
    • runnpm view aicut-cli
      • runnode /usr/bin/npm view aicut-cli
        • secretread ~/.npmrc (its own config)
        • netregistry.npmjs.org:443 sent 389 B
    • runhead
    • runnpm view aicut-cli dist-tags
      • runnode /usr/bin/npm view aicut-cli dist-tags
        • secretread ~/.npmrc (its own config)
        • netregistry.npmjs.org:443 sent 389 B
  • runbash -c curl -s -o /dev/null -w "%{http_code}\n" https://registry...
    • runcurl -s -o /dev/null -w %{http_code}\n
      • netregistry.npmjs.org:443 sent 90 B
    • runcurl -s https://registry.npmjs.org/aicut-cli
      • netregistry.npmjs.org:443 sent 90 B
    • runhead -c 500
    • runcurl -s https://registry.npmjs.org/-/v1/search?text=aicut&size=10
      • netregistry.npmjs.org:443 sent 111 B
      • netDNS lookups for npmjs.org 16 queries
    • runhead -c 1500
  • runbash -c ls -la; echo "=== skill dir ==="; ls -R ./skill 2>/dev/nu...
    • runls -la
    • runls -R ./skill
    • runhead -40
    • runls /usr/lib/node_modules /usr/local/lib/node_modules
  • runbash -c cat skill/references/setup.md; echo "=== README ==="; cat...
    • runcat skill/references/setup.md
    • runcat README.md
    • runcat package.json
    • runls -la src
  • runbash -c cat skill/references/spend.md; echo "=== meta ==="; cat s...
    • runcat skill/references/spend.md
    • runcat skill/_meta.json

Exploration log

1 run
  1. llm:baseline ok · 56.5s

    new behavior: dns:registry.npmjs.org, exec:curl, ownread:~/.npmrc, write:~/.npm/_cacache/content-v2/sha512/91/ac/* · 8 model steps, 8 commands

    $ aicut --version; echo "---"; aicut account $ node --version; npm --version; npm i -g aicut-cli 2>&1 | tail -20 $ npm view aicut-cli version 2>&1 | tail -5; echo "---"; npm config get registry; echo "---"; cat /var/tmp/detonator-runs/ad42274ab0d5466ea432fc40bf2030db/home/.npm/_logs/*debug-0.log 2>/dev/null | tail $ npm view aicut-cli 2>&1 | head -40; echo "=== dist-tags ==="; npm view aicut-cli dist-tags 2>&1 | head $ curl -s -o /dev/null -w "%{http_code}\n" https://registry.npmjs.org/aicut-cli; curl -s https://registry.npmjs.org/aicut-cli | head -c 500; echo; echo "=== search ==="; curl -s "https://registry.npmjs. $ ls -la; echo "=== skill dir ==="; ls -R ./skill 2>/dev/null | head -40; echo "=== which ==="; ls /usr/lib/node_modules /usr/local/lib/node_modules 2>/dev/null; command -v aicut aicut-cli $ cat skill/references/setup.md; echo "=== README ==="; cat README.md; echo "=== package.json ==="; cat package.json; echo "=== src ==="; ls -la src $ cat skill/references/spend.md; echo "=== meta ==="; cat skill/_meta.json model said: The npm registry in this environment is a proxy that returns no package data. Let me check whether the CLI exists anywhere locally.

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.