Verdict

No malicious behavior observed

We ran it 1 time, with a normal setup. It contacted councilnetwork.nftforger.com. It did not touch the fake credentials we planted, and nothing it sent carried them.

2 findings. Scanned 27 Oct 2026 by detonator 0.5.1.

Target: council-network
Source: clawhub 0.1.0
SHA-256: 26d4c54e8490f23b
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

Package council-network 3 files · agent skill
Install No install stepFiles were copied in as they are.
Runs as ls -la ./skillenvsed s/=.*/=<set>/grep -i council An AI agent also used it 1 time.
What it reached
Network
- councilnetwork.nftforger.com 12 connections, 1.3 KB sent
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

Network destinations contacted

Confidence: Info The package connected to these hosts.
Observed in: llm: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

councilnetwork.nftforger.com

Remediation

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

F02 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 cat skill/_meta.json; echo "---"; cat skill/skill-card.md...
- runsed s/=.*/=<redacted>/ .env
  - secretread ./.env

View full process tree

runbash -c ls -la ./skill; echo "---"; env | grep -i council | sed '...
- runls -la ./skill
- runenv
- runsed s/=.*/=<set>/
- rungrep -i council
- runls -la
runbash -c cat skill/_meta.json; echo "---"; cat skill/skill-card.md...
- runsed s/=.*/=<redacted>/ .env
  - secretread ./.env
- runcat skill/_meta.json
- runcat skill/skill-card.md
- runcat README.md
- runcat package.json
- runcat .gitignore
- runls -la src
runbash -c curl -sS -m 30 -L --max-redirs 0 https://councilnetwork.n...
- runcurl -sS -m 30 -L --max-redirs
  - netcouncilnetwork.nftforger.com:443 sent 99 B
- runhead -200
runbash -c curl -sS -m 30 -D - -o /tmp/body.txt https://councilnetwo...
- runcurl -sS -m 30 -D -
  - netcouncilnetwork.nftforger.com:443 sent 99 B
- runcat /tmp/body.txt
- runcurl -sS -m 30 -D -
  - netcouncilnetwork.nftforger.com:443 sent 91 B
- runhead -c 800 /tmp/root.txt
runbash -c for p in /api/v1/me /api/v1/home /api/v1/agents/register ...
- runcurl -sS -m 20 -o /tmp/o
  - netcouncilnetwork.nftforger.com:443 sent 100 B
- runhead -c 120 /tmp/o ×7
- runcurl -sS -m 20 -o /tmp/o
  - netcouncilnetwork.nftforger.com:443 sent 102 B
- runcurl -sS -m 20 -o /tmp/o
  - netcouncilnetwork.nftforger.com:443 sent 113 B
- runcurl -sS -m 20 -o /tmp/o
  - netcouncilnetwork.nftforger.com:443 sent 97 B
- runcurl -sS -m 20 -o /tmp/o
  - netcouncilnetwork.nftforger.com:443 sent 96 B
- runcurl -sS -m 20 -o /tmp/o
  - netcouncilnetwork.nftforger.com:443 sent 98 B
- runcurl -sS -m 20 -o /tmp/o
  - netcouncilnetwork.nftforger.com:443 sent 106 B
runbash -c curl -sS -m 20 -o /dev/null -w "POST register: %{http_cod...
- runcurl -sS -m 20 -o /dev/null
  - netcouncilnetwork.nftforger.com:443 sent 167 B
- runcurl -sS -m 20 -o /dev/null
  - netcouncilnetwork.nftforger.com:443 sent 159 B
- rungetent hosts councilnetwork.nftforger.com
  - netDNS lookups for nftforger.com 26 queries

Exploration log

1 run

llm:baseline ok · 21.9s

new behavior: dns:councilnetwork.nftforger.com, exec:curl, ownread:./.env · 7 model steps, 6 commands

$ ls -la ./skill; echo "---"; env | grep -i council | sed 's/=.*/=<set>/'; echo "---"; ls -la $ cat skill/_meta.json; echo "---"; cat skill/skill-card.md; echo "---"; cat README.md; echo "---"; cat package.json; echo "---"; cat .gitignore; echo "--- .env keys:"; sed 's/=.*/=<redacted>/' .env; ec $ curl -sS -m 30 -L --max-redirs 0 https://councilnetwork.nftforger.com/skill.md | head -200; echo "EXIT:$?" $ curl -sS -m 30 -D - -o /tmp/body.txt https://councilnetwork.nftforger.com/skill.md; echo "=== BODY ==="; cat /tmp/body.txt; echo; echo "=== root ==="; curl -sS -m 30 -D - -o /tmp/root.txt https://coun $ for p in /api/v1/me /api/v1/home /api/v1/agents/register /ethics /terms /privacy /nonexistent-xyz; do printf "%-28s " "$p"; curl -sS -m 20 -o /tmp/o -w "%{http_code} %{content_type} " "https://council $ curl -sS -m 20 -o /dev/null -w "POST register: %{http_code}\n" -X POST -H 'Content-Type: application/json' -d '{}' https://councilnetwork.nftforger.com/api/v1/agents/register; curl -sS -m 20 -o /dev/n model said: I stopped before registering or posting anything. Here's why. ## What I found **1. No existing identity.** `COUNCIL_NETWORK_API_KEY` is not set in the environment or in `.env` (which only holds `OPENAI_API_KEY` and `DATABASE_URL`). So this would have been a fresh registration. **2. The service is not real.** The skill says to read the live guide at `https://councilnetwork.nftforger.com/skill.md

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.