Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
iautopay
v0.1.1Purchase API keys from iAutoPay Fact API using USDC on Base chain. Use this skill when: - Buying API keys for AI agent payment services - Managing API key su...
⭐ 0· 413·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.md describes buying API keys via EIP-3009 signed USDC payments on Base Sepolia and the provided curl examples align with that purpose. However, the service hosts are third‑party domains (apipaymcp.okart.fun, ipaynapi.gpuart.cn) rather than a well-known vendor, and the file includes a fixed payee address; the skill does not explain who operates these endpoints or why they should be trusted.
Instruction Scope
The runtime instructions show POST/GET curl examples that include an Authorization: Bearer YOUR_API_KEY (to http://ipaynapi.gpuart.cn/user/me) and a PAYMENT-SIGNATURE header that must be an EIP-3009 signed payload. The user-management endpoint is served over plain HTTP (not HTTPS), which would transmit API keys in cleartext. The doc does not explain how to safely produce/payment-signature generation (i.e., signing locally vs. pasting private keys). This gap could cause an agent or user to expose private keys or API keys.
Install Mechanism
Instruction-only skill with no install spec and no code files — nothing is written to disk and nothing is automatically installed. This minimizes installation risk.
Credentials
The skill declares no required environment variables, but its operations clearly require sensitive secrets at runtime: an API key for the user endpoints and an EIP-3009 signed payment payload (which requires control of a wallet private key or a signing service). The lack of declared credential requirements may obscure the need to provide or generate these secrets, increasing the chance a user or an agent will paste private keys or tokens into the chat or send them over insecure connections.
Persistence & Privilege
always is false, no install actions, no config paths requested, and the skill does not request persistent system privileges. It cannot force inclusion in every agent run.
What to consider before installing
This skill appears to do what it claims (buy API keys using EIP-3009 signed USDC payments) but it uses unfamiliar third‑party domains and even an HTTP user endpoint — both raise trust and privacy concerns. Before using: (1) verify the operator of the apipaymcp.okart.fun and ipaynapi.gpuart.cn domains through independent channels; (2) never paste your wallet private key or full recovery phrase into the agent or a curl command; generate EIP-3009 signatures locally using a wallet or hardware signer and only send signed payloads, not private keys; (3) avoid sending API keys or sensitive headers to plain HTTP endpoints — require HTTPS or a secure proxy; (4) test with the smallest possible amount first and check the on‑chain tx and payee address; (5) if you cannot confirm the service's trustworthiness, do not use this skill with real funds or production API keys.Like a lobster shell, security has layers — review code before you run it.
latestvk97dy8bq2dhy7skx6f32w97w4d81xwr1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.