Verdict
No malicious behavior observed
We ran it 8 times, with a normal setup, LC_MESSAGES set, docs:--seed 20240501 --start-date 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
- huawei-cloud-study-plan-generate
- Source
- clawhub 1.0.0
- SHA-256
- 4b681be4a5c14db6
- Files
- 12
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 huawei-cloud-study-plan-generate 12 files · agent skill
- Install No install stepFiles were copied in as they are.
- Runs as python3 <skill>/scripts/generate_study_plan.pypython3 <skill>/scripts/generate_study_plan.py --seed 20240501 --start-datepython3 <skill>/tests/test_generate_study_plan.py/usr/bin/python3 <skill>/scripts/generate_study_plan.py --seed 1 --days 0
-
What it reached
Network
No connections.
CredentialsNone of the planted fake keys were touched.
Files written- ./plan.mdwritten
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:guided:LC_MESSAGESEvery 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
- runpython3 <skill>/tests/test_generate_study_plan.py
- run/usr/bin/python3 <skill>/scripts/generate_study_plan.py --seed 1 --days 0
- run/usr/bin/python3 <skill>/scripts/generate_study_plan.py --seed 20240501 --start-date 2026-10-24
- run/usr/bin/python3 <skill>/scripts/generate_study_plan.py --seed 1 --days 1
- run/usr/bin/python3 <skill>/scripts/generate_study_plan.py --seed 42 --days 2
- run/usr/bin/python3 <skill>/scripts/generate_study_plan.py --help
- run/usr/bin/python3 <skill>/scripts/generate_study_plan.py --seed 42 --days 2
Exploration log
8 runs-
scripts:baseline ok · 1.4s
no new behavior
-
scripts:guided:LC_MESSAGES ok · 1.2s
no new behavior
-
scripts:docs:--seed 20240501 --start-date ok · 1.1s
no new behavior
-
scripts:baseline ok · 6.3s
new behavior: write:<skill>/tests/_tmp_output.md, write:<skill>/tests/_tmp_topics.json
-
scripts:guided:LC_MESSAGES ok · 8.7s
no new behavior
-
scripts:time-travel ok · 9.2s
no new behavior
-
obedient:baseline ok · 14.9s
new behavior: write:./plan.md
$ python3 scripts/generate_study_plan.py --seed 20240501 --start-date 2026-10-24 python3 scripts/generate_study_plan.py --seed 42 --format text python3 scripts/generate_study_plan.py --seed 42 --format -
obedient:guided:LC_MESSAGES ok · 13.9s
no new behavior
$ python3 scripts/generate_study_plan.py --seed 20240501 --start-date 2026-10-24 python3 scripts/generate_study_plan.py --seed 42 --format text python3 scripts/generate_study_plan.py --seed 42 --format
scripts/scripts/generate_study_plan.py: coverage plateau (2 runs with no new behavior); scripts/tests/test_generate_study_plan.py: coverage plateau (2 runs with no new behavior); obedient: 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.