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

Verdict

No malicious behavior observed

We ran it 1 time, with a normal setup. It made no network connections. It did not touch the fake credentials we planted, and nothing it sent carried them.

0 findings. Scanned 27 Oct 2026 by detonator 0.5.1.

Target
dutis
Source
clawhub 1.0.0
SHA-256
b5dcb431c00ff787
Files
3
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 1 run
  1. Package dutis 3 files · agent skill
  2. Install No install stepFiles were copied in as they are.
  3. Runs as ls skillwhich dutishead -50cat skill/_meta.json skill/skill-card.md An AI agent also used it 1 time.
  4. 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 llm: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
  • runbash -c cd . && ls skill && which dutis; dutis doctor --json 2>&1...
    • runls skill
    • runwhich dutis
    • runhead -50
  • runbash -c cd . && cat skill/_meta.json skill/skill-card.md; ls -la;...
    • runcat skill/_meta.json skill/skill-card.md
    • runls -la
    • runls /usr/local/bin /opt/homebrew/bin
    • runhead -50
  • runbash -c cd . && cat README.md package.json .gitignore; ls src; un...
    • runcat README.md package.json .gitignore
    • runls src
    • rununame -a
    • runcat /etc/os-release
    • runhead -3
  • runbash -c cd . && ls ~/.local/bin /opt 2>/dev/null; find / -maxdept...
    • runls ~/.local/bin /opt
    • runhead
    • runfind / -maxdepth 4 -name dutis*

Exploration log

1 run
  1. llm:baseline ok · 30.2s

    no new behavior · 5 model steps, 4 commands

    $ cd . && ls skill && which dutis; dutis doctor --json 2>&1 | head -50 $ cd . && cat skill/_meta.json skill/skill-card.md; ls -la; ls /usr/local/bin /opt/homebrew/bin 2>/dev/null | head -50 $ cd . && cat README.md package.json .gitignore; ls src; uname -a; cat /etc/os-release 2>/dev/null | head -3 $ cd . && ls ~/.local/bin /opt 2>/dev/null; find / -maxdepth 4 -name 'dutis*' -not -path '*/proc/*' 2>/dev/null | head; sw_vers 2>&1 | head -2 model said: I couldn't run the Dutis workflow, because this environment can't support it. **What I found** - The skill is installed at `./skill` (Dutis v1.0.0, publisher tsonglew), but the `dutis` CLI is not installed (`dutis: command not found`), and no `dutis*` binary exists anywhere on the system. - This machine is **Ubuntu 24.04 Linux (x86_64)**, not macOS. Dutis manages macOS Launch Services association

llm: variants exhausted

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.