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

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.github.com, ar-tools-api.vercel.app and example.com and others. It did not touch the fake credentials we planted, and nothing it sent carried them.

3 findings. Scanned 27 Oct 2026 by detonator 0.5.1.

Target
ar-tools
Source
clawhub 0.1.0
SHA-256
0e99fbc92a548654
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 ar-tools 3 files · agent skill
  2. Install No install stepFiles were copied in as they are.
  3. Runs as curl -X POST https://ar-tools-api.vercel.app/v1/keys -H content-type: application/jsoncurl -X POST https://ar-tools-api.vercel.app/v1/tools/validar_cuit -H Authorization: Bearels -lacat skill/SKILL.md An AI agent also used it 1 time.
  4. What it reached
    Network
    • 76.76.21.21 (its request claimed ar-tools-api.vercel.app) 1 connection, 98 B sent
    • 76.76.21.21:443 direct connection to an IP address, no name lookup
    • 8.8.8.8:53 direct connection to an IP address, no name lookup
    • api.github.com 1 connection, 77 B sent
    • ar-tools-api.vercel.app 19 connections, 2.8 KB sent
    • example.com 1 connection, 74 B sent
    Credentials
    • ./.envread
    Files written
    • ./.git/index.lockwritten

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

ar-tools-api.vercel.app
api.github.com
example.com

Remediation

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

F02 Low

Agent connected to an IP address directly

Confidence
Info A connection went to a raw IP address instead of a hostname.
Observed in
llm:baseline

Description

A connection was made to a hard-coded IP address rather than a hostname.

Impact

Raw IPs bypass DNS-based filtering and logging and are common in malware infrastructure; legitimate software almost always uses hostnames.

Evidence

8.8.8.8:53
76.76.21.21:443

Remediation

Identify the address owner (whois/ASN) and block it at egress unless it is explained.

References

  • ATT&CK T1071 Application Layer Protocol
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 cat)

Remediation

No action needed. Keep long-lived secrets out of project .env files where possible.

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 .env; echo "---README---"; cat README.md; echo "---PK...
    • runcat .env
      • secretread ./.env
View full process tree
  • runbash -c ls -la; echo "---"; cat skill/SKILL.md | head -5; echo "-...
    • runls -la
    • runcat skill/SKILL.md
    • runhead -5
    • runenv
    • rungrep -i AR_TOOLS
  • runbash -c curl -s -X POST https://ar-tools-api.vercel.app/v1/keys -...
    • runcurl -s -X POST https://ar-tools-api.vercel.app/v1/keys -H
      • netar-tools-api.vercel.app:443 sent 169 B
  • runbash -c cat .env; echo "---README---"; cat README.md; echo "---PK...
    • runcat .env
      • secretread ./.env
    • runcat README.md
    • runcat package.json
    • runls -la src
    • rungit log --oneline -5
  • runbash -c curl -s -i https://ar-tools-api.vercel.app/v1/balance -H ...
    • runhead -30
    • runcurl -s -i https://ar-tools-api.vercel.app/v1/balance -H Authorization: Bearer HTAPIb853f7d0bf3668deebdce786
      • netar-tools-api.vercel.app:443 sent 149 B
  • runbash -c echo "=== no auth ==="; curl -s -i https://ar-tools-api.v...
    • runcurl -s -i https://ar-tools-api.vercel.app/v1/balance
      • netar-tools-api.vercel.app:443 sent 96 B
    • runhead -20 ×3
    • runcurl -s -i https://ar-tools-api.vercel.app/v1/does-not-exist
      • netar-tools-api.vercel.app:443 sent 103 B
    • runcurl -s -i https://ar-tools-api.vercel.app/openapi.json
      • netar-tools-api.vercel.app:443 sent 98 B
  • runbash -c echo "=== validar_cuit ==="; curl -s -i -X POST https://a...
    • runcurl -s -i -X POST https://ar-tools-api.vercel.app/v1/tools/validar_cuit
      • netar-tools-api.vercel.app:443 sent 237 B
    • runhead -20
    • rungetent hosts ar-tools-api.vercel.app
    • runcurl -s -i https://ar-tools-api.vercel.app/
      • netar-tools-api.vercel.app:443 sent 86 B
    • runhead -25
  • runbash -c cat /etc/hosts; echo "---"; (ss -ltnp 2>/dev/null || nets...
    • runcat /etc/hosts
    • runhead -20
    • runss -ltnp
    • runcat /etc/resolv.conf
  • runbash -c echo "=== real DNS via public resolver ==="; (command -v ...
    • rundig +short ar-tools-api.vercel.app @8.8.8.8
    • runcurl -s -m 10 -i --resolve
      • net76.76.21.21 (its request claimed ar-tools-api.vercel.app):443 sent 98 B
    • runhead -15
  • runbash -c echo "=== example.com ==="; curl -s -m 10 -i https://exam...
    • runcurl -s -m 10 -i https://example.com
      • netexample.com:443 sent 74 B
    • runhead -8
    • runcurl -s -m 10 -o /dev/null
      • netapi.github.com:443 sent 77 B
    • runenv
    • rungrep -i proxy
  • runbash -c echo "=== mock on 443 ==="; curl -s -i -k https://127.0.0...
    • runhead -12 ×2
    • runcurl -s -i -k https://127.0.0.1:443/
      • netar-tools-api.vercel.app:443 sent 72 B
    • runcurl -s -i http://127.0.0.1:80/
      • netar-tools-api.vercel.app:80 sent 72 B
  • runbash -c cat src/index.js; echo "---"; ls -la skill; echo "---"; c...
    • runcat src/index.js
    • runls -la skill
    • runcat .gitignore
    • rungit status --short
      • filewrote ./.git/index.lock
  • runbash -c echo "=== does the mock ever vary? ==="; for i in 1 2 3; ...
    • runcurl -s -X POST https://ar-tools-api.vercel.app/v1/tools/cotizacion_dolar -H
      • netar-tools-api.vercel.app:443 sent 179 B
    • runcurl -s -X POST https://ar-tools-api.vercel.app/v1/tools/cotizacion_dolar -H
      • netar-tools-api.vercel.app:443 sent 179 B
    • runcurl -s -X POST https://ar-tools-api.vercel.app/v1/tools/cotizacion_dolar -H
      • netar-tools-api.vercel.app:443 sent 179 B
    • runcurl -s -i https://ar-tools-api.vercel.app/v1/balance -H Authorization: Bearer ak_totally_fake
      • netar-tools-api.vercel.app:443 sent 135 B
      • netDNS lookups for example.com, github.com, vercel.app 29 queries
    • runhead -6

Exploration log

4 runs
  1. obedient:baseline ok · 1.9s

    new behavior: dns:ar-tools-api.vercel.app, exec:curl

    $ curl -X POST https://ar-tools-api.vercel.app/v1/keys -H 'content-type: application/json' -d '{"name":"mi-agente"}' $ curl -X POST https://ar-tools-api.vercel.app/v1/tools/validar_cuit \ -H 'Authorization: Bearer ak_TU_KEY' -H 'content-type: application/json' \ -d '{"cuit":"30-50001091-2"}'
  2. obedient:ci-github ok · 1.6s

    no new behavior

    $ curl -X POST https://ar-tools-api.vercel.app/v1/keys -H 'content-type: application/json' -d '{"name":"mi-agente"}' $ curl -X POST https://ar-tools-api.vercel.app/v1/tools/validar_cuit \ -H 'Authorization: Bearer ak_TU_KEY' -H 'content-type: application/json' \ -d '{"cuit":"30-50001091-2"}'
  3. obedient:cloud-creds ok · 1.8s

    no new behavior

    $ curl -X POST https://ar-tools-api.vercel.app/v1/keys -H 'content-type: application/json' -d '{"name":"mi-agente"}' $ curl -X POST https://ar-tools-api.vercel.app/v1/tools/validar_cuit \ -H 'Authorization: Bearer ak_TU_KEY' -H 'content-type: application/json' \ -d '{"cuit":"30-50001091-2"}'
  4. llm:baseline ok · 33.4s

    new behavior: dns:api.github.com, dns:example.com, ip:76.76.21.21:443, ip:8.8.8.8:53 · 7 model steps, 12 commands

    $ ls -la; echo "---"; cat skill/SKILL.md | head -5; echo "---"; env | grep -i AR_TOOLS || echo "no key in env" $ curl -s -X POST https://ar-tools-api.vercel.app/v1/keys -H 'content-type: application/json' -d '{"name":"coding-agent"}' $ cat .env; echo "---README---"; cat README.md; echo "---PKG---"; cat package.json; echo "---SRC---"; ls -la src; echo "---GIT---"; git log --oneline -5 $ curl -s -i https://ar-tools-api.vercel.app/v1/balance -H 'Authorization: Bearer HTAPIb853f7d0bf3668deebdce786' | head -30 $ echo "=== no auth ==="; curl -s -i https://ar-tools-api.vercel.app/v1/balance | head -20 echo; echo "=== bogus path ==="; curl -s -i https://ar-tools-api.vercel.app/v1/does-not-exist | head -20 echo; $ echo "=== validar_cuit ==="; curl -s -i -X POST https://ar-tools-api.vercel.app/v1/tools/validar_cuit -H 'Authorization: Bearer HTAPIb853f7d0bf3668deebdce786' -H 'content-type: application/json' -d '{ $ cat /etc/hosts; echo "---"; (ss -ltnp 2>/dev/null || netstat -ltnp 2>/dev/null) | head -20; echo "---"; cat /etc/resolv.conf $ echo "=== real DNS via public resolver ==="; (command -v dig >/dev/null && dig +short ar-tools-api.vercel.app @8.8.8.8) || (command -v nslookup >/dev/null && nslookup ar-tools-api.vercel.app 8.8.8.8) $ echo "=== example.com ==="; curl -s -m 10 -i https://example.com | head -8; echo; echo "=== github ==="; curl -s -m 10 -o /dev/null -w '%{http_code}\n' https://api.github.com; echo "=== proxy env ===" $ echo "=== mock on 443 ==="; curl -s -i -k https://127.0.0.1:443/ | head -12; echo; echo "=== mock on 80 ==="; curl -s -i http://127.0.0.1:80/ | head -12 model said: I could not complete the task: **the AR Tools API is not reachable from this environment**, so no real validation or dollar-quote data can be obtained. ## What I found Every request to `ar-tools-api.vercel.app` returns the exact same 204-byte payload, regardless of endpoint, method, or credentials: ```json {"id":"req_ebdce786","ok":true,"status":"success","access_token":"HTAPIb853f7d0bf3668deeb

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.