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

Verdict

No malicious behavior observed

We ran it 8 times, with a normal setup, a GitHub Actions environment, cloud credentials present, a production environment and a GitLab CI environment. It contacted app.feedbackpulse.com 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
feedbackpulse
Source
clawhub 1.0.0
SHA-256
d99baeab2733889e
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
  1. Package feedbackpulse 3 files · agent skill
  2. Install No install stepFiles were copied in as they are.
  3. Runs as npx -y mcp-remote https://app.feedbackpulse.com/mcp/employee-surveysnode /usr/bin/npx -y mcp-remote https://app.feedbackpulse.com/mcp/employee-surveysls -lals -la skill An AI agent also used it 1 time.
  4. What it reached
    Network
    • app.feedbackpulse.com 6 connections, 1.7 KB sent
    • registry.npmjs.org 19 connections, 5.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 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, 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
app.feedbackpulse.com

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, 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 npx)
~/.npmrc (by npm, npx)

Remediation

No action needed.

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

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 skill/_meta.json; echo "---"; cat skill/skill-card.md...
    • runsed s/=.*/=<redacted>/ .env
      • secretread ./.env
View full process tree
  • runbash -c ls -la; echo "---"; ls -la skill; echo "---"; cat skill/S...
    • runls -la
    • runls -la skill
    • runcat skill/SKILL.md
    • runhead -50
  • runbash -c cat skill/_meta.json; echo "---"; cat skill/skill-card.md...
    • runsed s/=.*/=<redacted>/ .env
      • secretread ./.env
    • runcat skill/_meta.json
    • runcat skill/skill-card.md
    • runcat README.md
    • runcat package.json
    • runls -la src
    • runcat .gitignore
  • runbash -c cd /tmp && curl -sS -m 30 -X POST https://app.feedbackpul...
    • runhead -60
    • runcurl -sS -m 30 -X POST
      • netapp.feedbackpulse.com:443 sent 342 B
  • runbash -c cd /tmp && curl -sS -m 30 -X POST https://app.feedbackpul...
    • runcurl -sS -m 30 -X POST
      • netapp.feedbackpulse.com:443 sent 247 B
    • runhead -c 3000
  • runbash -c cd /tmp && for p in /mcp /mcp/employee-surveys; do echo "...
    • runcurl -sS -m 30 -o /dev/null
      • netapp.feedbackpulse.com:443 sent 325 B
    • runcurl -sS -m 30 -o /dev/null
      • netapp.feedbackpulse.com:443 sent 342 B
    • runcurl -sS -m 30 -o /dev/null
      • netapp.feedbackpulse.com:443 sent 104 B
  • runbash -c cd /tmp && curl -sS -m 30 -X POST https://app.feedbackpul...
    • runcurl -sS -m 30 -X POST
      • netapp.feedbackpulse.com:443 sent 342 B
    • runpython3 -c import sys,json; d=json.load(sys.stdin); print(json.dumps...
  • runbash -c cd /tmp && timeout 120 npx -y [email protected] https://a...
    • runhead -80
    • runtimeout 120 npx -y [email protected] https://app.feedbackpulse.com/mcp/employee-surveys
      • runnpx -y [email protected] https://app.feedbackpulse.com/mcp/employee-surveys
        • runnode /usr/bin/npx -y [email protected] https://app.feedbackpulse.com/mcp/employee-surveys
          • secretread ~/.npmrc (its own config)
          • netregistry.npmjs.org:443 sent 433 B
          • netregistry.npmjs.org:443 sent 447 B
  • runbash -c cd /tmp && timeout 60 npm view mcp-remote version 2>&1 | ...
    • runtimeout 60 npm view mcp-remote version
      • runnpm view mcp-remote version
        • runnode /usr/bin/npm view mcp-remote version
          • secretread ~/.npmrc (its own config)
          • netregistry.npmjs.org:443 sent 391 B
    • runtail -3
    • runtimeout 60 npm view mcp-remote dist-tags
      • runnpm view mcp-remote dist-tags
        • runnode /usr/bin/npm view mcp-remote dist-tags
          • secretread ~/.npmrc (its own config)
          • netregistry.npmjs.org:443 sent 391 B
          • netDNS lookups for feedbackpulse.com, npmjs.org 18 queries
    • runtail -5

Exploration log

8 runs
  1. obedient:baseline ok · 20.3s

    new behavior: dns:registry.npmjs.org, ownread:~/.npmrc, write:~/.npm/_cacache/content-v2/sha512/d6/96/*, write:~/.npm/_cacache/index-v5/2b/da/*

    $ npx -y mcp-remote https://app.feedbackpulse.com/mcp/employee-surveys
  2. obedient:ci-github ok · 17.9s

    new behavior: write:~/.npm/_cacache/content-v2/sha512/31/cc/*, write:~/.npm/_cacache/tmp/866dfc7b

    $ npx -y mcp-remote https://app.feedbackpulse.com/mcp/employee-surveys
  3. obedient:cloud-creds ok · 20.3s

    new behavior: write:~/.npm/_cacache/content-v2/sha512/08/13/*, write:~/.npm/_cacache/tmp/36170d33

    $ npx -y mcp-remote https://app.feedbackpulse.com/mcp/employee-surveys
  4. obedient:production ok · 13.2s

    new behavior: write:~/.npm/_cacache/content-v2/sha512/f3/d0/*

    $ npx -y mcp-remote https://app.feedbackpulse.com/mcp/employee-surveys
  5. obedient:ci-gitlab ok · 16.8s

    new behavior: write:~/.npm/_cacache/content-v2/sha512/46/d8/*, write:~/.npm/_cacache/tmp/7a0fde23

    $ npx -y mcp-remote https://app.feedbackpulse.com/mcp/employee-surveys
  6. obedient:time-travel ok · 15.8s

    no new behavior

    $ npx -y mcp-remote https://app.feedbackpulse.com/mcp/employee-surveys
  7. obedient:everything ok · 14.2s

    new behavior: write:~/.npm/_cacache/content-v2/sha512/9c/54/*, write:~/.npm/_cacache/tmp/0c9fa228

    $ npx -y mcp-remote https://app.feedbackpulse.com/mcp/employee-surveys
  8. llm:baseline ok · 47.5s

    new behavior: dns:app.feedbackpulse.com, exec:curl, ownread:./.env, write:~/.npm/_cacache/content-v2/sha512/42/21/* · 8 model steps, 8 commands

    $ ls -la; echo "---"; ls -la skill; echo "---"; cat skill/SKILL.md | head -50 $ cat skill/_meta.json; echo "---"; cat skill/skill-card.md; echo "---"; cat README.md; echo "---"; cat package.json; echo "---"; ls -la src; echo "---"; cat .gitignore; echo "--- env keys:"; sed 's/=.* $ cd /tmp && curl -sS -m 30 -X POST https://app.feedbackpulse.com/mcp/employee-surveys \ -H 'Content-Type: application/json' \ -H 'Accept: application/json, text/event-stream' \ -d '{"jsonrpc":"2. $ cd /tmp && curl -sS -m 30 -X POST https://app.feedbackpulse.com/mcp/employee-surveys \ -H 'Content-Type: application/json' \ -H 'Accept: application/json, text/event-stream' \ -d '{"jsonrpc":"2. $ cd /tmp && for p in /mcp /mcp/employee-surveys; do echo "== $p"; curl -sS -m 30 -o /dev/null -w '%{http_code} %{content_type}\n' -X POST "https://app.feedbackpulse.com$p" -H 'Content-Type: application $ cd /tmp && curl -sS -m 30 -X POST https://app.feedbackpulse.com/mcp/employee-surveys -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"m $ cd /tmp && timeout 120 npx -y [email protected] https://app.feedbackpulse.com/mcp/employee-surveys 2>&1 <<'EOF' | head -80 {"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"20 $ cd /tmp && timeout 60 npm view mcp-remote version 2>&1 | tail -3; echo "---"; timeout 60 npm view mcp-remote dist-tags 2>&1 | tail -5 model said: I'll start by looking at the project and the skill files to see what's available.

obedient: variants exhausted; 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.