Back to skill

Security audit

paddock-check-payee

Security checks for vulnerabilities and agentic risk

Overview

This skill is a narrow payee-check helper that sends disclosed x402 payment fields to Paddock before payment, with no bundled code, persistence, or hidden install behavior.

Install only if you are comfortable sharing the x402 resource URL and payment terms with Paddock for verification. The skill can help catch mismatched payee wallets, but users handling sensitive payment relationships may want an explicit policy or self-hosted alternative before enabling it broadly.

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
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The skill instructs the agent to send sensitive payment metadata (url, payTo, network, asset, and amount) to a third-party Paddock endpoint, but it does not explicitly warn that this discloses transaction and counterparty details outside the original payment flow. Even if the service is legitimate and the check is useful, this creates a privacy and operational data-leak risk because endpoint relationships, wallet addresses, and payment terms may be exposed without user awareness or consent.

Content

No source excerpt is available for this finding.