External Transmission
- Category
- Data Exfiltration
- Confidence
- 84% confidence
- Finding
The API transmission itself is expected for a news skill, but the surrounding instructions tell the agent to sign a payment using the amount and recipient supplied in an HTTP 402 response without specifying spending limits, recipient validation, or prior user authorization. If the agent has wallet-signing authority, a compromised endpoint or manipulated payment response could induce unauthorized payments; this is a payment-authorization weakness rather than evidence of data exfiltration.
- Content
md Base URL: https://api.quorumz.com 1. Read the free catalog: GET https://api.quorumz.com/api/agent/v1 2. Call the route you need with no payment header. 3. If the response is HTTP 402, read the PAYMENT-REQUIRED header. It is base64 JSON. Its accepts list USDC on Base (eip155:8453), Polygon (eip155:137) and Arbitrum (eip155:42161): sign the exact amount to the payTo address on the one you hold, then retry the same URL with PAYMENT-SIGNATURE. 4. Read PAYMENT-RESPONSE for the settlement receipt.
