fluxa-agent-wallet-via-api

HIGH W007: Insecure credential handling detected in skill instructions.

• Insecure credential handling detected (high risk: 0.90). The skill explicitly requires using an Agent JWT as an Authorization: Bearer header in API calls (and shows curl/header examples), which instructs the agent to include a secret token verbatim in requests/commands, creating exfiltration risk.

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

• Third-party content exposure detected (high risk: 0.90). The skill's x402 payment flow (X402-PAYMENT.md) requires the agent to call arbitrary paid APIs, parse their HTTP 402 responses (e.g., accepts[...] fields, host/resource) such as the concrete example fluxa-x402-api.gmlgtm.workers.dev, and use those fields to construct payments and subsequent requests—clearly ingesting untrusted third-party responses that can alter agent actions.

MEDIUM W012: Unverifiable external dependency detected (runtime URL that controls agent).

• Potentially malicious external URL detected (high risk: 0.90). The runtime API call to https://walletapi.fluxapay.xyz/api/mandates/create-intent can return a payment_model_context containing registration instructions, so remote content from that URL can directly control agent prompts at runtime.

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

• Direct money access detected (high risk: 1.00). This skill is explicitly designed to perform on-chain financial operations. It defines concrete API endpoints and authentication (Agent JWT) and lists capabilities such as x402 payments, sending USDC payouts to any wallet address, transferring USDC to another agent by Agent ID, and creating payment links to receive payments. Those are specific crypto/payment actions (wallet payouts, payment links, and protocol payments), not generic tooling, so it grants direct financial execution authority.