Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Use this skill when the user wants to purchase a virtual debit card using crypto, create a prepaid card via x402 protocol, check virtual card status, or set up an EVM wallet for card payments. Trigger on: "buy a card", "get a virtual card", "create card", "card status", "setup wallet for card", or any intent involving purchasing virtual Visa/Mastercard with cryptocurrency.
v1.0.0Use this skill when the user wants to purchase a virtual debit card using crypto, create a prepaid card via x402 protocol, check virtual card status, or set...
⭐ 0· 49·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill is for buying virtual cards via an x402 HTTP/blockchain flow and needs an EVM private key and Node/npx to sign payments and run the published CLI. Requesting EVM_PRIVATE_KEY and node/npx is consistent with the stated purpose.
Instruction Scope
Runtime instructions direct the agent to run npx @aeon-ai-pay/x402-card commands (setup, create, status) and to store the private key in ~/.x402-card/config.json. They also instruct an automatic background 'upgrade --check' that may trigger an 'upgrade' run. The background auto-upgrade and the explicit suggestion to pass private keys on CLI flags (which can leak to shell history or process listings) expand the risk surface beyond just local signing and status checks.
Install Mechanism
There is no bundled code; the skill repeatedly instructs running npx which downloads and executes code from the npm registry at runtime. That is a normal pattern for CLI tools but it means arbitrary code can be fetched/ran (especially via the auto-upgrade path) — a higher-risk install mechanism compared with instruction-only local actions.
Credentials
Only EVM_PRIVATE_KEY is declared as the primary credential, which is proportionate to signing payments. However, handling private keys via CLI flags, env vars, and a local config file increases exposure; the SKILL.md's assurances (masked display, stored with 600 perms) are helpful but do not eliminate risk of accidental leakage or exfiltration if the remotely fetched CLI is malicious or compromised.
Persistence & Privilege
The skill does not request always:true and does not modify other skills. The notable behavior is running a one-per-session background auto-upgrade check which can autonomously fetch/execute code; this increases runtime privilege but is limited to the skill's own CLI workflow.
What to consider before installing
This skill appears to do what it says (create virtual cards by signing payments), but exercise caution before using it with a wallet that holds real funds. Specific recommendations:
- Use a dedicated, low-value wallet for card purchases — do not use your main wallets.
- Prefer setting the private key in a local config file with strict permissions or an environment variable rather than passing it as a CLI flag (flags can be stored in shell history or visible in process lists).
- Review the npm package @aeon-ai-pay/x402-card and its GitHub repo (verify publisher, recent commits, and package integrity) before running npx commands. The skill's auto-upgrade runs npx upgrade and can fetch/execute new code without further prompts — consider disabling or scrutinizing upgrades.
- If possible, use a signing device or hardware wallet flow rather than embedding raw private keys in files/flags.
- Don’t store large balances in the wallet used with this skill; test with small amounts first. If you want, provide the package source or the npm package link so a further code-level review can reduce uncertainty.Like a lobster shell, security has layers — review code before you run it.
latestvk977qjjzaqpfa9n38sejxw4dbh843hm1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Binsnode, npx
Primary envEVM_PRIVATE_KEY