Verdict

No malicious behavior observed

We ran it 8 times, with a normal setup, a GitHub Actions environment and cloud credentials present. 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: scan-watermark-removal
Source: clawhub 1.0.0
SHA-256: a5cbb616a0887022
Files: 12

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

Package scan-watermark-removal 12 files · agent skill
Install No install stepFiles were copied in as they are.
Runs as python3 <skill>/scripts/remove_watermark.pypython3 <skill>/scripts/verify_batch.pypython3 <skill>/scripts/wm_pdf.py
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 scripts: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

runpython3 <skill>/scripts/remove_watermark.py

Exploration log

8 runs

scripts:baseline ok · 0.7s

no new behavior
scripts:ci-github ok · 0.9s

no new behavior
scripts:cloud-creds ok · 0.8s

no new behavior
scripts:baseline ok · 0.6s

no new behavior
scripts:ci-github ok · 1.1s

no new behavior
scripts:cloud-creds ok · 0.6s

no new behavior
scripts:baseline ok · 0.6s

no new behavior
scripts:ci-github ok · 0.7s

no new behavior

scripts/scripts/remove_watermark.py: coverage plateau (2 runs with no new behavior); scripts/scripts/verify_batch.py: coverage plateau (2 runs with no new behavior); scripts/scripts/wm_pdf.py: run budget spent; llm: run budget spent

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.