ClawHub
Back to skill

Security audit

Agent Payment Error Preview

Security checks for vulnerabilities and agentic risk

Overview

This is a small payment-error triage guide that discloses its paid upgrade path and does not include code that runs, persists, or accesses secrets by itself.

Before using the skill, keep payment logs redacted as it advises. The paid upgrade path is clearly promotional, so install the paid package only if you trust that separate listing and need live corpus-backed diagnosis.

A.I.G

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

SkillSpector

Vulnerability Patterns
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • 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)

Autonomous Decision Making

Medium
Category
Excessive Agency
Content
## Anti-patterns

- Treating HTTP 401 like a normal API-key failure without checking EIP-712 domain mismatch.
- Reusing EIP-3009 nonces across attempts.
- Caching an agent-payment mandate or session token across merchants.
- Hard-coding MCP tool IDs instead of refreshing manifests per session.
Confidence
75% confidence
Finding
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Static analysis

No suspicious patterns detected.