Verdict

No malicious behavior observed

We ran it 8 times, with a normal setup, the clock moved a year ahead, a GitHub Actions environment, cloud credentials present and a production environment. It contacted api.github.com, github.com and registry.npmjs.org. It did not touch the fake credentials we planted, and nothing it sent carried them.

4 findings. Scanned 27 Oct 2026 by detonator 0.5.1.

Target: social-media-specs
Source: clawhub 1.0.0
SHA-256: 9d869af14ae61e4f
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 8 runs

Package social-media-specs 3 files · agent skill
Install No install stepFiles were copied in as they are.
Runs as npx social-media-specs fit <caption>node /usr/bin/npx social-media-specs fit <caption>npx social-media-specs media instagram-reel 1080x1920 --videonode /usr/bin/npx social-media-specs media instagram-reel 1080x1920 An AI agent also used it 1 time.
What it reached
Network
- api.github.com 1 connection, 112 B sent
- github.com 3 connections, 306 B sent
- registry.npmjs.org 20 connections, 6.4 KB sent
Credentials
- ./.envread
~/.npmrc read by its own tool (normal)
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

Used a planted key with the service it belongs to (registry.npmjs.org)

Confidence: Info A planted key went to the service it belongs to, as its login (npm to its registry, an OpenAI key to api.openai.com).
Observed in: obedient:baseline

Description

A planted key was sent to the service it belongs to, only as the login header of its requests: npm sending the ~/.npmrc token to registry.npmjs.org while installing, or an app calling api.openai.com with the OpenAI key from .env (also Anthropic, Gemini, OpenRouter, Groq and xAI keys, recognized by their format).

Impact

Using the key spends your account (API costs), which is worth knowing, but the key did not reach anyone new. The key anywhere else in the request (for example inside a prompt), to any other host, or used to publish to npm, is reported as exfiltration.

Evidence

~/.npmrc (npm) sent only as the login header of requests to registry.npmjs.org

Remediation

No action needed.

F02 Low

Network destinations contacted

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

registry.npmjs.org

api.github.com

github.com

Remediation

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

F03 Low

A tool read its own credentials (e.g. gh, aws, ssh)

Confidence: Info A tool opened its own login or config file, such as npm reading ~/.npmrc.
Observed in: obedient:baseline, llm:baseline

Description

A tool opened its own configuration or login file, such as npm reading ~/.npmrc or gh reading its hosts file.

Impact

None in itself: this is how those tools work. Listed so the report shows every credential access.

Evidence

~/.npmrc (by npx)

~/.npmrc (by npm, npx)

Remediation

No action needed.

F04 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 cat)

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 package.json; echo "---"; cat README.md; echo "---"; ...
- runcat .env
  - secretread ./.env

View full process tree

runbash -c ls -la; echo "---"; ls -la skill; echo "---"; cat skill/S...
- runls -la
- runls -la skill
- runhead -5
- runcat skill/SKILL.md
- runnode --version
- runnpx --version
  - runnode /usr/bin/npx --version
    - secretread ~/.npmrc (its own config)
runbash -c cat package.json; echo "---"; cat README.md; echo "---"; ...
- runcat .env
  - secretread ./.env
- runcat package.json
- runcat README.md
- runls -la src
- runcat skill/_meta.json
- runcat skill/skill-card.md
- runsed s/=.*/=<redacted>/
runbash -c cd /tmp && timeout 90 npx --yes [email protected] ...
- runtimeout 90 npx --yes [email protected] --help
  - runnpx --yes [email protected] --help
    - runnode /usr/bin/npx --yes [email protected] --help
      - secretread ~/.npmrc (its own config)
      - netregistry.npmjs.org:443 sent 433 B
      - netregistry.npmjs.org:443 sent 463 B
- runhead -40
runbash -c cd /tmp && timeout 60 npm view social-media-specs version...
- runhead -20
- runtimeout 60 npm view social-media-specs version
  - runnpm view social-media-specs version
    - runnode /usr/bin/npm view social-media-specs version
      - secretread ~/.npmrc (its own config)
      - netregistry.npmjs.org:443 sent 407 B
- runhead -40
- runtimeout 60 npm view social-media-specs
  - runnpm view social-media-specs
    - runnode /usr/bin/npm view social-media-specs
      - secretread ~/.npmrc (its own config)
      - netregistry.npmjs.org:443 sent 407 B
runbash -c cd /tmp && timeout 60 npm view social-media-specs version...
- runtimeout 60 npm view social-media-specs version
  - runnpm view social-media-specs version
    - runnode /usr/bin/npm view social-media-specs version
      - secretread ~/.npmrc (its own config)
      - netregistry.npmjs.org:443 sent 407 B
- runtimeout 30 curl -sS -o /dev/null
  - runcurl -sS -o /dev/null -w %{http_code}\n
    - netregistry.npmjs.org:443 sent 99 B
runbash -c cd /tmp && timeout 30 curl -sS https://registry.npmjs.org...
- runtimeout 30 curl -sS https://registry.npmjs.org/social-media-specs
  - runcurl -sS https://registry.npmjs.org/social-media-specs
    - netregistry.npmjs.org:443 sent 99 B
- runhead -c 600
- runtimeout 30 curl -sS -o /dev/null
  - runcurl -sS -o /dev/null -w %{http_code}\n
    - netgithub.com:443 sent 102 B
runbash -c cd /tmp && timeout 30 curl -sS https://github.com/hermoso...
- rungrep -oE <title>[^<]*</title>
- runhead -3
- runtimeout 30 curl -sS https://github.com/hermoso-ai/social-media-specs
  - runcurl -sS https://github.com/hermoso-ai/social-media-specs
    - netgithub.com:443 sent 102 B
- runtimeout 30 curl -sS https://api.github.com/repos/hermoso-ai/social-media-specs
  - runcurl -sS https://api.github.com/repos/hermoso-ai/social-media-specs
    - netapi.github.com:443 sent 112 B
- runhead -c 800
runbash -c cd /tmp && timeout 30 curl -sS -D - -o /dev/null https://...
- runhead -20 ×2
- runtimeout 30 curl -sS -D -
  - runcurl -sS -D - -o /dev/null
    - netregistry.npmjs.org:443 sent 99 B
- runtimeout 30 curl -sS -D -
  - runcurl -sS -D - -o /dev/null
    - netgithub.com:443 sent 102 B
    - netDNS lookups for github.com, npmjs.org 22 queries

Exploration log

8 runs

obedient:baseline ok · 20.3s

new behavior: dns:registry.npmjs.org, ownread:~/.npmrc, write:~/.npm/_cacache/content-v2/sha512/07/6b/*, write:~/.npm/_cacache/index-v5/d1/ef/*

$ npx social-media-specs fit "<caption>" # every channel at once npx social-media-specs media instagram-reel 1080x1920 --video --seconds 40 npx social-media-specs ad meta.pr
obedient:time-travel ok · 20.3s

no new behavior

$ npx social-media-specs fit "<caption>" # every channel at once npx social-media-specs media instagram-reel 1080x1920 --video --seconds 40 npx social-media-specs ad meta.pr
obedient:ci-github ok · 20.3s

new behavior: write:~/.npm/_cacache/content-v2/sha512/2e/f3/*, write:~/.npm/_cacache/tmp/b34c9ee1

$ npx social-media-specs fit "<caption>" # every channel at once npx social-media-specs media instagram-reel 1080x1920 --video --seconds 40 npx social-media-specs ad meta.pr
obedient:cloud-creds ok · 20.3s

new behavior: write:~/.npm/_cacache/content-v2/sha512/4e/8f/*, write:~/.npm/_cacache/tmp/f7b365c2

$ npx social-media-specs fit "<caption>" # every channel at once npx social-media-specs media instagram-reel 1080x1920 --video --seconds 40 npx social-media-specs ad meta.pr
obedient:production ok · 20.3s

new behavior: write:~/.npm/_cacache/content-v2/sha512/92/0b/*, write:~/.npm/_cacache/tmp/ae853e19

$ npx social-media-specs fit "<caption>" # every channel at once npx social-media-specs media instagram-reel 1080x1920 --video --seconds 40 npx social-media-specs ad meta.pr
obedient:ci-gitlab ok · 20.3s

new behavior: write:~/.npm/_cacache/content-v2/sha512/3a/a4/*, write:~/.npm/_cacache/tmp/4f3d0310

$ npx social-media-specs fit "<caption>" # every channel at once npx social-media-specs media instagram-reel 1080x1920 --video --seconds 40 npx social-media-specs ad meta.pr
obedient:everything ok · 20.3s

new behavior: write:~/.npm/_cacache/content-v2/sha512/99/f0/*, write:~/.npm/_cacache/tmp/2a488a05

$ npx social-media-specs fit "<caption>" # every channel at once npx social-media-specs media instagram-reel 1080x1920 --video --seconds 40 npx social-media-specs ad meta.pr
llm:baseline ok · 53.9s

new behavior: dns:api.github.com, dns:github.com, exec:curl, ownread:./.env · 8 model steps, 8 commands

$ ls -la; echo "---"; ls -la skill; echo "---"; cat skill/SKILL.md | head -5; echo "---"; node --version; npx --version $ cat package.json; echo "---"; cat README.md; echo "---"; ls -la src; echo "---"; cat skill/_meta.json; echo "---"; cat skill/skill-card.md; echo "---"; cat .env | sed 's/=.*/=<redacted>/' $ cd /tmp && timeout 90 npx --yes [email protected] --help 2>&1 | head -40; echo "EXIT:$?" $ cd /tmp && timeout 60 npm view social-media-specs version 2>&1 | head -20; echo "---"; timeout 60 npm view social-media-specs 2>&1 | head -40 $ cd /tmp && timeout 60 npm view social-media-specs version; echo "EXIT:$?"; timeout 30 curl -sS -o /dev/null -w "%{http_code}\n" https://registry.npmjs.org/social-media-specs 2>&1 $ cd /tmp && timeout 30 curl -sS https://registry.npmjs.org/social-media-specs | head -c 600; echo; echo "---"; timeout 30 curl -sS -o /dev/null -w "%{http_code}\n" https://github.com/hermoso-ai/social- $ cd /tmp && timeout 30 curl -sS https://github.com/hermoso-ai/social-media-specs | grep -oE '<title>[^<]*</title>' | head -3; echo "---"; timeout 30 curl -sS https://api.github.com/repos/hermoso-ai/soc $ cd /tmp && timeout 30 curl -sS -D - -o /dev/null https://registry.npmjs.org/social-media-specs 2>&1 | head -20; echo "---"; timeout 30 curl -sS -D - -o /dev/null https://github.com/hermoso-ai/social-m model said: I'll start by looking at the skill directory and the project to see what's available.

obedient: variants exhausted; 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.