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.

1 finding. Scanned 26 Oct 2026 by detonator 0.5.1.

Target
vista-computer-use
Source
clawhub 1.0.0
SHA-256
42c3634a259751fb
Files
4
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 1 run
  1. Package vista-computer-use 4 files · agent skill
  2. Install No install stepFiles were copied in as they are.
  3. Runs as ls -lals -la ./skilluname -als -la ~/.codex An AI agent also used it 1 time.
  4. What it reached
    Network

    No connections.

    Credentials
    • ./.envread
    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

F01 Low

Loaded the project's .env file

Confidence
Info The package loaded the project's .env file.
Observed in
llm:baseline

Description

The process loaded the project's .env file. Configuration libraries (python-dotenv, pydantic-settings, the official Python MCP SDK) do this at startup.

Impact

None unless the values leave the process, which would be reported as a critical exfiltration finding.

Evidence

./.env (by sed)

Remediation

No action needed. Keep long-lived secrets out of project .env files where possible.

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.

  • runbash -c echo "--- .env keys (names only) ---"; sed 's/=.*/=<redac...
    • runsed s/=.*/=<redacted>/ .env
      • secretread ./.env
View full process tree
  • runbash -c pwd; echo "---"; ls -la; echo "--- skill ---"; ls -la ./s...
    • runls -la
    • runls -la ./skill
    • rununame -a
  • runbash -c echo "--- MCP configs ---"; ls -la ~/.codex 2>/dev/null; ...
    • runls -la ~/.codex
    • runcat ~/.codex/config.toml
    • runls -la ~/.config
    • runhead -50
    • runenv
    • rungrep -i -E mcp|vista
  • runbash -c cat skill/_meta.json; echo "---"; cat skill/skill-card.md...
    • runcat skill/_meta.json
    • runcat skill/skill-card.md
    • runcat README.md
    • runcat package.json
    • runls -la src
    • runcat .gitignore
  • runbash -c echo "--- any vista/mcp binaries ---"; which vista vista-...
    • runwhich vista vista-desktop-mcp codex claude
    • runls /opt
    • runhead -30
    • runss -ltnp
    • runls /tmp/.X11-unix
  • runbash -c echo "--- .env keys (names only) ---"; sed 's/=.*/=<redac...
    • runsed s/=.*/=<redacted>/ .env
      • secretread ./.env
    • runcat src/index.js
    • rungit log --oneline -5
  • runbash -c echo "--- MCP tool availability check ---"; ls ~/.mcp* /e...
    • runls ~/.mcp* /etc/mcp*
    • runhead
    • runfind / -maxdepth 4 -iname *vista*
    • runhead -2
    • runpython3 -c import mcp; print('mcp installed', mcp.__file__)
    • runnode -v

Exploration log

1 run
  1. llm:baseline ok · 18.5s

    new behavior: ownread:./.env · 4 model steps, 6 commands

    $ pwd; echo "---"; ls -la; echo "--- skill ---"; ls -la ./skill 2>/dev/null; echo "--- OS ---"; uname -a $ echo "--- MCP configs ---"; ls -la ~/.codex 2>/dev/null; cat ~/.codex/config.toml 2>/dev/null; echo "---"; ls -la ~/.config 2>/dev/null | head -50; echo "--- env ---"; env | grep -i -E 'mcp|vista' $ cat skill/_meta.json; echo "---"; cat skill/skill-card.md; echo "--- README ---"; cat README.md; echo "--- pkg ---"; cat package.json; echo "--- src ---"; ls -la src; echo "--- gitignore ---"; cat .gi $ echo "--- any vista/mcp binaries ---"; which vista vista-desktop-mcp codex claude 2>/dev/null; ls /opt 2>/dev/null; echo "--- listening ports ---"; (ss -ltnp 2>/dev/null || netstat -ltnp 2>/dev/null) $ echo "--- .env keys (names only) ---"; sed 's/=.*/=<redacted>/' .env; echo "--- src/index.js ---"; cat src/index.js; echo "--- git log ---"; git log --oneline -5 2>/dev/null $ echo "--- MCP tool availability check ---"; ls ~/.mcp* /etc/mcp* 2>/dev/null; find / -maxdepth 4 -iname '*vista*' -not -path '/proc/*' 2>/dev/null | head; echo "--- python mcp pkg ---"; python3 -c "im model said: I checked the environment before attempting any desktop action. Here's what I found: **The VISTA Desktop MCP is not connected, so I can't perform a desktop task.** Evidence: - **No `vista_desktop` tools are available to me.** My only tool is a shell (`bash`). The skill's first step — "Discover the connected vista_desktop tools" — fails, and the skill explicitly says: *"If unavailable, report the

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.