Skills/ClawHub/btcd-skill-beta

btcd-skill-beta@1.0.0

VERIFIED· install only

Publisher claims: "Run the BTCD collateralization flow on PGP chain. Use when the user asks to run a BTCD loan, collateralization flow, create/take orders, lock BTC, submit pro..." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry ClawHubPublisher contact-nbwfoundation · publishing for 268 daysInstalls 1,446Last detonated 23 min ago
$clawhub install btcd-skill-beta
WatchReport an issue

Coverage

Bundled scripts ran with no arguments; no agent task scenario for this bundle.
Tested
install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · 8 of 14 bundled scripts run with no arguments (the rest were not run: per-bundle cap), with decoy credentials in the environment · every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (3 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-18 and scored it 84/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 1 s · 3 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessinstall script run in the sandbox
0.1sprocessexited 1: Node.js v22.23.5
0.1sprocessbundled script run in the sandbox with no arguments
0.2sprocessexited 1: Node.js v22.23.5
0.2sprocessbundled script run in the sandbox with no arguments
0.3sprocessexited 1: Node.js v22.23.5
0.3sprocessbundled script run in the sandbox with no arguments
0.4sprocessexited 1: Node.js v22.23.5
0.4sprocessbundled script run in the sandbox with no arguments
0.5sprocessexited 1: Node.js v22.23.5
0.5sprocessbundled script run in the sandbox with no arguments
0.6sprocessexited 1: Node.js v22.23.5
0.6sprocessbundled script run in the sandbox with no arguments
0.7sprocessexited 1: Node.js v22.23.5
0.7sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.8sprocessexited 1: Node.js v22.23.5
0.8sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.9sprocessexited 1: Node.js v22.23.5
0.9sprocess8 of 14 bundled scripts run with no arguments (the rest were not run: per-bundle cap)
0.9sprocessscript backend runs setup only
0.9sprocessscript backend runs setup only
1.0sprocesssecond launch, clock +45 days, CI unset
1.1sprocessexited 1: Node.js v22.23.5

Static findings

HIGH
Access to sensitive file pathsSKILL.md:17 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files├── .env.template.txtFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
File type combined with upload actionSKILL.md:116 · File type combined with upload action — agent may exfiltrate local data files- Checks `state/flow-state.json` first. If a `btcTxId` already exists, it resumes confirmation waiting instead of sending new BTC.Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07
HIGH
Access to sensitive file pathsscripts/setup.js:45 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system fileslogger.info(' OR set ORDER_ID in .env and run: npm run 01-take-order (to take existing order)');Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsscripts/utils/config.js:8 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files// Load .env file from the test-flow directoryFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsSKILL.md:38 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files2. **Create `.env`** from the template. Only two values need changing:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsSKILL.md:42 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesEdit `.env` and set:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsSKILL.md:40 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filescp .env.template.txt .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsscripts/utils/config.js:9 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesdotenv.config({ path: join(__dirname, '..', '.env') });Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsscripts/01-take-order.js:31 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesthrow new Error('No order ID found. Either run 00-create-order or set ORDER_ID in .env');Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈1,875 tok
1 file · 24 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.