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

Verdict

No malicious behavior observed

We ran it 8 times, with a normal setup, LC_MESSAGES and REQUEST_METHOD and SSLKEYLOGFILE set, docs:--format text --top, docs:--format json --top and a GitHub Actions environment. It contacted 60s.viki.moe. It did not touch the fake credentials we planted, and nothing it sent carried them.

1 finding. Scanned 27 Oct 2026 by detonator 0.5.1.

Target
huawei-cloud-daily-hot-topics
Source
clawhub 1.0.0
SHA-256
c99fe2604cfadbf0
Files
12
RecommendationNo action needed

Nothing observed calls for action. This is evidence, not a guarantee.

batch:clawhub:2026-10-27

What this package does

observed across 8 runs
  1. Package huawei-cloud-daily-hot-topics 12 files · agent skill
  2. Install No install stepFiles were copied in as they are.
  3. Runs as python3 <skill>/scripts/fetch_hot_topics.pypython3 <skill>/scripts/fetch_hot_topics.py --format text --toppython3 <skill>/scripts/fetch_hot_topics.py --format json --toppython3 <skill>/tests/test_fetch_hot_topics.py
  4. What it reached
    Network
    • 60s.viki.moe 63 connections, 11.2 KB sent
    Credentials

    None of the planted fake keys were touched.

    Files written
    • ./HTENVj0tgNGNPRfGPuWvzupGuRSaKwritten
    • ./hot.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

F01 Low

Network destinations contacted

Confidence
Info The package connected to these hosts.
Observed in
scripts:baseline

Description

Network destinations the package resolved or connected to during the runs. All traffic was captured by the sandbox; nothing reached the internet.

Impact

Context only. Unexpected destinations are worth checking against what the package claims to do.

Evidence

60s.viki.moe

Remediation

Confirm each host is expected (the package's API, its registry). Allowlist expected egress in production.

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/fetch_hot_topics.py
    • net60s.viki.moe:443 sent 181 B ×6
    • net60s.viki.moe:443 sent 182 B ×3
    • netDNS lookups for viki.moe 18 queries

Exploration log

8 runs
  1. scripts:baseline ok · 1.8s

    new behavior: dns:60s.viki.moe

  2. scripts:guided:LC_MESSAGES,REQUEST_METHOD,SSLKEYLOGFILE ok · 1.5s

    new behavior: write:./HTENVj0tgNGNPRfGPuWvzupGuRSaK

  3. scripts:docs:--format text --top ok · 1.3s

    no new behavior

  4. scripts:docs:--format json --top ok · 1.3s

    no new behavior

  5. scripts:baseline ok · 1.9s

    new behavior: write:./hot.json

  6. scripts:guided:LC_MESSAGES,REQUEST_METHOD,SSLKEYLOGFILE ok · 2.1s

    no new behavior

  7. scripts:ci-github ok · 2.0s

    no new behavior

  8. obedient:baseline ok · 14.2s

    new behavior: write:./hot.md

    $ python3 scripts/fetch_hot_topics.py python3 scripts/fetch_hot_topics.py --format text --top 5 python3 scripts/fetch_hot_topics.py --format json --top 3 python3 scripts/fetch_hot_topics.py --source zhi

scripts/scripts/fetch_hot_topics.py: coverage plateau (2 runs with no new behavior); scripts/tests/test_fetch_hot_topics.py: coverage plateau (2 runs with no new behavior); obedient: 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.