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

Verdict

Could not run: not tested

We could not start this server, so none of its behavior was tested. It said: Error [ERR_REQUIRE_ESM]: require() of ES Module /var/tmp/detonator-runs/17326930051c409c89655e81c2174c24/work/skill/node_modules/@xrplf/isomorphic/node_modules/@noble/hashes/utils.js from /var/tmp/detonator-runs/17326930051c409c8965

0 findings. Scanned 25 Oct 2026 by detonator 0.5.1.

Target
lumi-trades-mcp
Source
npm 0.9.7
SHA-256
d316d1473665de2a
Files
8
RecommendationReview

We could not start it, so nothing was tested. Treat it as unverified.

What this package does

observed across 3 runs
  1. Package lumi-trades-mcp version 0.9.7 · 8 files · MCP server
  2. Install No install scripts of its ownOnly the package manager ran.
  3. Runs as node src/index.js
  4. What it reached
    Network

    No connections.

    Credentials

    None of the planted fake keys were touched.

    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

No findings. Detonator observed no malicious or suspicious behavior in the runs below.

Process tree

run mcp: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 npm_config_update_notifier=false npm_config_audit=...
    • runnpm rebuild --offline --foreground-scripts --no-audit --no-fund
      • runnode /usr/bin/npm rebuild --offline --foreground-scripts --no-audit
  • runbash -c node skill/node_modules/lumi-trades-mcp/src/index.js
    • runnode skill/node_modules/lumi-trades-mcp/src/index.js

Exploration log

3 runs
  1. mcp:baseline ok · 2.7s

    new behavior: write:~/.npm/_logs/*-debug-0.log · server did not complete the handshake: no response; server crashed: Error [ERR_REQUIRE_ESM]: require() of ES Module /var/tmp/detonator-runs/17326930051c409c89655e81c2174c24/work/skill/node_modules/@xrplf/isomorphic/node_modules/@noble/hashes/utils.js from /var/tmp/detonator-runs/17326930051c409c8965

  2. mcp:time-travel ok · 2.8s

    no new behavior · server did not complete the handshake: no response; server crashed: Error [ERR_REQUIRE_ESM]: require() of ES Module /var/tmp/detonator-runs/a8bc7058440743f48c121c93c5e0e4e5/work/skill/node_modules/@xrplf/isomorphic/node_modules/@noble/hashes/utils.js from /var/tmp/detonator-runs/a8bc7058440743f48c12

  3. mcp:ci-github ok · 2.4s

    no new behavior · server did not complete the handshake: no response; server crashed: Error [ERR_REQUIRE_ESM]: require() of ES Module /var/tmp/detonator-runs/78d6c7a7a86241c48bc408dae258e58f/work/skill/node_modules/@xrplf/isomorphic/node_modules/@noble/hashes/utils.js from /var/tmp/detonator-runs/78d6c7a7a86241c48bc4

mcp: coverage plateau (2 runs with no new behavior)

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.