addr-standardize

Fail

Audited by Snyk on Aug 18, 2026

Risk Level: CRITICAL
Full Analysis

CRITICAL E005: Suspicious download URL detected in skill instructions.

  • Suspicious download URL detected (high risk: 0.90). One of the URLs is a direct script download (https://fittings.sh/skill/call.mjs) and the skill explicitly instructs users to curl and run it — fetching and executing code from a remote host is a high-risk pattern; the other URLs are API/catalog endpoints.

MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).

  • Third-party content exposure detected (low risk: 0.10). The required runtime workflow (addr.standardize -> call.mjs -> fetches https://fittings.sh/v1/addr/standardize with user-provided address) ingests outsider-authored free text as the address request payload, but it is not used to fetch or read other outsider-authored content.

MEDIUM W009: Direct money access capability detected (payment gateways, crypto, banking).

  • Direct money access detected (high risk: 1.00). The skill explicitly includes an on-chain payment flow: it returns a 402 quote, requires signing an authorization, and documents using a private key (FITTINGS_PRIVATE_KEY) and a wallet holding USDC on Base. It references @x402/evm and shows a real call that will sign and spend funds. Those are specific crypto-wallet signing/payment instructions (direct financial execution), not merely generic HTTP or browser automation.

Issues (3)

E005
CRITICAL

Suspicious download URL detected in skill instructions.

W011
MEDIUM

Third-party content exposure detected (indirect prompt injection risk).

W009
MEDIUM

Direct money access capability detected (payment gateways, crypto, banking).

Audit Metadata
Risk Level
CRITICAL
Analyzed
Aug 18, 2026, 05:15 AM
Issues
3