Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Query the PolyOx API for NBA data, Polymarket predictions, and AI matchup analysis. The analysis endpoint uses the x402 payment protocol (USDC on Base Sepolia).

v0.2.0

Query the PolyOx API for NBA data, Polymarket predictions, and AI matchup analysis. The analysis endpoint uses the x402 payment protocol (USDC on Base Sepolia).

0· 366·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
high confidence
Purpose & Capability
The skill name/description (PolyOx NBA data + Polymarket + x402 paid analysis) matches the SKILL.md instructions: free REST endpoints plus a paid analysis endpoint using x402 (USDC on Base Sepolia). Requiring wallet access to sign x402 payments is coherent with the stated purpose. However, the skill metadata declares no required environment variables or primary credential while the runtime instructions explicitly ask the user/agent to set EVM_PRIVATE_KEY or install a wallet — this metadata/instruction mismatch is notable.
!
Instruction Scope
SKILL.md instructs the agent/user to: (a) set an EVM_PRIVATE_KEY env var (private key access), (b) install and use a third-party Coinbase Agentic Wallet CLI via npx (which itself requests email/OTP), and (c) perform EIP-712 signing and send signatures in request headers. These steps require access to secrets and to install/execute third-party tooling; the document also gives concrete shell commands (curl, base64, jq). The instructions therefore reach beyond simple read-only API queries into signing transactions and private-key handling — which is high-sensitivity behavior and should have been declared in metadata.
Install Mechanism
The skill itself has no install spec and is instruction-only (lower static install risk), but it explicitly tells the agent/user to run npx to add the coinbase/agentic-wallet-skills and to use npx awal@latest commands. Prompting installation of third-party npm packages at runtime is a moderate risk (pulling and executing external code). There is no pinned/verified package version in the SKILL.md excerpt and no attestations about the third-party package's provenance.
!
Credentials
The paid x402 flow legitimately requires signing with an EVM private key or using a wallet; requesting EVM_PRIVATE_KEY is proportionate to performing the payment. But the skill metadata lists no required environment variables while the instructions explicitly reference EVM_PRIVATE_KEY and wallet installation. That mismatch can cause an agent to read secrets that weren't declared as required. Also the guidance to authenticate via email with a third-party wallet CLI (npx) introduces additional secret exchange/credential flows that are not described in the metadata.
Persistence & Privilege
The skill does not request 'always: true' and offers no install spec or files to persist into the agent. Autonomous invocation is allowed (platform default) but not by itself a red flag here. The skill does instruct installing an external wallet CLI, but that is an action outside the skill's bundle, not a built-in persistence request by the skill itself.
What to consider before installing
What to consider before installing/using this skill: - The skill's runtime instructions require signing payments with an EVM private key or installing a third-party wallet CLI, but the skill metadata does not declare any required credentials — treat that mismatch as a warning sign. Do not set your mainnet private key (EVM_PRIVATE_KEY) in an environment accessible to shared agents or services. - Prefer using a throwaway/testnet wallet (Base Sepolia) and fund it with small test USDC amounts before any real use. Never use production/mainnet funds unless you fully trust the code and endpoints. - If you must use the Coinbase Agentic Wallet CLI: verify the package name, author, version, and source repository before running npx; consider auditing that package separately. Using npx runs remote code on your machine — confirm the package integrity and pin versions. - Review and trust the API host (https://api-hoobs.polyox.io) before sending requests that trigger payments. Confirm domain ownership / docs and check for HTTPS/TLS validity. - Because the SKILL.md instructs the agent to access/handle private keys and install tooling, you should either: (a) refuse to provide secrets and use only the skill's free, read-only endpoints; or (b) perform an independent security review of the third-party wallet tooling and the PolyOx API before handing over any private key or running any installation commands. - If you want to change the risk profile: request the maintainer add explicit metadata (required.env includes EVM_PRIVATE_KEY or a clear note that no env var is required and only agentic wallet will be used), and provide a reproducible, auditable wallet integration path (e.g., signed releases, pinned package versions).

Like a lobster shell, security has layers — review code before you run it.

latestvk979br5j1kr6qs466m5kevk4h98249cp

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments