Back to skill

Security audit

x402 Lotto

Security checks for vulnerabilities and agentic risk

Overview

This lottery API skill is mostly coherent, but it can enable USDC payments without clearly requiring user confirmation or spend limits.

Review this carefully before installing. Use only a limited wallet or test funds, confirm which x402.lotto endpoints charge USDC before calling them, and avoid giving the skill access to a wallet key that can spend more than you intend.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (1)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The skill documents a payment-enabled API client and even shows code that wraps fetch with payment, but it does not warn users that some requests may initiate purchases or spend funds. This can lead to unintended financial transactions, especially if users treat the example as a normal read-only API call pattern and do not realize the client may automatically authorize x402 payments.

Content

No source excerpt is available for this finding.