Caveat verdict
smithnode
Requires git, cargo, network, filesystem, and shell permissions to operate a P2P blockchain validator node that participates in a live network; while the skill explicitly says never send private keys, the broad capability scope and network participation in an external blockchain are above what a typical tool warrants.
⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.
Automated static analysis — not a human review. Caveat flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.
Permission integrity
credential_access
Findings (8)
Pipe-to-shell pattern (curl | sh) — supply chain attack vector
DEPLOYMENT.md · code · curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
Pipe to sh — executes piped content as shell commands
DEPLOYMENT.md · code · | sh
Pipe to python — executes piped content as Python code
VALIDATOR_GUIDE.md · code · | python3
References sudo — requests elevated privileges
DEPLOYMENT.md · code · sudo
Downloads executables from external URLs
DEPLOYMENT.md · code · Download from https://
HTTP request to bare IP address — common in malicious payloads
DEPLOYMENT.md · code · http://127.0.0.1
Opens WebSocket connection
README.md · code · WebSocket
Uses exec() — may execute shell commands
VALIDATOR_GUIDE.md · prose · downgraded · exec(
Why the tier is capped
Execution sink present in raw bytes (Hard Floor: class A/B). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.
Permissions & capabilities
No declared permissions — minimal attack surface.
credential_access Is this flag fair?
Thanks — recorded.