Neckr0ik X402 Payments
Security checks across static analysis, malware telemetry, and agentic risk
Overview
This payment skill asks for wallet-level authority and advertises autonomous stablecoin payments, but the artifacts under-declare key handling and the visible code appears to simulate rather than verify real payments.
Do not provide a real funded wallet private key to this skill unless the publisher clarifies secure key handling, real payment settlement, approval controls, budgets, and provenance. If testing, use dry-run mode and a dedicated low-balance wallet only.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A user or agent could believe a real payment was made or settled when the included implementation only generated a simulated receipt.
The visible code explicitly simulates blockchain payment and signatures while still reporting payment success, which conflicts with the documentation's claims about settled stablecoin payments.
# Simulate payment (in real implementation, would use blockchain) ... signature="simulated" ... print(f"Payment successful: {receipt.transaction_hash[:16]}...")Treat this as a demo until the publisher clearly documents and implements real signing, settlement, confirmation, and failure handling.
If a real funded wallet key is entered or exposed to the agent environment, mishandling could lead to loss of funds.
Wallet private keys are high-impact credentials, but the provided metadata declares no credential or environment-variable contract for this skill.
# Set wallet private key (stored securely) neckr0ik-x402-payments config set wallet.private_key <key> # Or use environment variable export X402_PRIVATE_KEY=<key>
Do not use a main wallet private key; require explicit credential declarations, secure storage details, and use only a dedicated low-balance wallet if testing.
If connected to a real wallet implementation, an agent could initiate payments to endpoints without a clear human approval boundary.
The documented behavior gives the agent autonomous financial action authority, but the artifacts do not define strong controls such as explicit approvals, trusted-recipient lists, or total spend budgets.
It enables AI agents to pay for API calls automatically using stablecoins, without accounts or human intervention.
Require user confirmation for every payment or configure strict allowlists, low per-call and total budgets, and dry-run-by-default behavior.
Users have less information to verify who maintains the payment code and how the advertised command should be safely installed or invoked.
The skill has limited provenance and no install/entrypoint specification, which is notable for software that asks users to configure payment credentials.
Source: unknown Homepage: none No install spec — this is an instruction-only skill.
Verify the publisher and source code independently before providing wallet-related credentials.