Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md scripts/x402-pay-with-memo.mjs
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a disclosed USDC shopping checkout integration with real spending and fulfillment risks, but I found no hidden or purpose-mismatched behavior.
Install only if you trust SP3ND with API credentials, wallet-based USDC payments, and shipping/contact details. Use a dedicated least-funded wallet, set explicit spending limits or human approval rules, pin or verify the package source before install, and remember that Collector Crypt payment is final before SP3ND manually completes NFT delivery.
Referenced artifact was not completely inspected
scripts/x402-pay-with-memo.mjs
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
The README describes an irreversible USDC payment flow for Collector Crypt cards where SP3ND manually acquires and later transfers the NFT, but it does not prominently warn users that payment finality occurs before delivery and that listing availability is not reserved. In this skill context, that omission is materially dangerous because agents may autonomously initiate blockchain payments, exposing users to custody, fulfillment, refund-delay, and non-delivery risk in a manual off-chain fulfillment step.
The sample code treats pricing_status === "quoted" as sufficient alongside payment_ready === true, even though the surrounding documentation says quoted is deprecated compatibility metadata and the canonical payable state is ready_for_payment. In a payment skill, examples are highly likely to be copied directly into implementations, so this inconsistency can cause clients to authorize payment under stale or ambiguous quote states, weakening the intended payment gating logic.
The manifest requires collection of sensitive personal data for shipped-product orders, including full name, recipient, physical address, phone number, and email, but does not present any explicit privacy notice, data handling disclosure, retention statement, or user-consent guidance. In a purchasing and fulfillment skill, this omission increases the risk of overcollection, unclear downstream sharing with fulfillment providers, and unsafe agent behavior that may request or transmit PII without adequately informing the user.
Detected: suspicious.env_credential_access