Verdict
No malicious behavior observed
We ran it 3 times, with a normal setup, the clock moved a year ahead and a GitHub Actions environment. It made no network connections. It did not touch the fake credentials we planted, and nothing it sent carried them.
0 findings. Scanned 25 Oct 2026 by detonator 0.5.1.
- Target
- mcp-exploit-demo
- Source
- github
- SHA-256
- d9771be562461305
- Files
- 3
Nothing observed calls for action. This is evidence, not a guarantee.
Findings
No findings. Detonator observed no malicious or suspicious behavior in the runs below.
Exploration log
3 runs-
mcp:baseline ok · 0.4s
no new behavior · server did not complete the handshake: no response; 0 tool calls
-
mcp:time-travel ok · 0.4s
no new behavior · server did not complete the handshake: no response; 0 tool calls
-
mcp:ci-github ok · 0.4s
no new behavior · server did not complete the handshake: no response; 0 tool calls
mcp: coverage plateau (2 runs with no new behavior)
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.