Verdict
No malicious behavior observed
We ran it 8 times, with a normal setup, WATCH_REPORT_DEPENDENCIES set and the clock moved a year ahead. It made no network connections. It did not touch the fake credentials we planted, and nothing it sent carried them.
0 findings. Scanned 26 Oct 2026 by detonator 0.5.1.
- Target
- mochi-study-coach
- Source
- clawhub 1.0.0
- SHA-256
- e214c1ffcb1a6f45
- Files
- 11
Nothing observed calls for action. This is evidence, not a guarantee.
batch:clawhub:2026-10-26
What this package does
observed across 8 runs- Package mochi-study-coach 11 files · agent skill
- Install No install stepFiles were copied in as they are.
- Runs as node <skill>/scripts/core.mjsnode <skill>/scripts/run.mjsnode <skill>/scripts/store.mjs
-
What it reached
Network
No connections.
CredentialsNone of the planted fake keys were touched.
Files writtenNothing 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 scripts:baselineEvery 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
- runnode <skill>/scripts/core.mjs
Exploration log
8 runs-
scripts:baseline ok · 0.8s
no new behavior
-
scripts:guided:WATCH_REPORT_DEPENDENCIES ok · 0.6s
no new behavior
-
scripts:time-travel ok · 0.8s
no new behavior
-
scripts:baseline ok · 0.9s
no new behavior
-
scripts:guided:WATCH_REPORT_DEPENDENCIES ok · 0.8s
no new behavior
-
scripts:time-travel ok · 1.0s
no new behavior
-
scripts:baseline ok · 1.1s
no new behavior
-
scripts:guided:WATCH_REPORT_DEPENDENCIES ok · 0.7s
no new behavior
scripts/scripts/core.mjs: coverage plateau (2 runs with no new behavior); scripts/scripts/run.mjs: coverage plateau (2 runs with no new behavior); scripts/scripts/store.mjs: run budget spent; llm: run budget spent
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.