ClawHub
Back to skill

Security audit

liquid-gas-sponsor

Security checks for vulnerabilities and agentic risk

Overview

This markdown-only skill clearly describes using a third-party Base paymaster to sponsor gas for USDC-paid transactions, with no hidden code or persistence.

Install only if you intend to use Liquid Agent's Base paymaster. Before paying or signing, confirm the quote, USDC amount, payTo address, chain ID, transaction target, value, gas limits, paymaster address, and any EIP-7702 authorization match what you asked for.

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
  • 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 (2)

External Transmission

Medium
Category
Data Exfiltration
Content
# Liquid gas sponsor — transact on Base with USDC only

Most agent wallets hold USDC and nothing else, and every on-chain action needs ETH for gas. This skill
removes that: **POST `https://api.liquidagent.ai/v1/gas`** is an ERC-4337 paymaster you pay **per
operation in USDC over x402**. The 402 is the quote. Pay it, sign what comes back, and the sponsor's
deposit pays the gas. No ETH, no account, no API key, no sign-up.
Confidence
78% confidence
Finding
The skill instructs users to POST transaction details to a third-party endpoint that returns signable payloads and sponsorship data. While this is the core function of the skill, it introduces a real trust boundary: a remote service can influence the operation contents, fee quote, authorization flow, and timing, which could lead to unintended transaction signing or payment authorization if clients do not independently validate returned fields.

External Transmission

Medium
Category
Data Exfiltration
Content
### Smart-wallet SDK (ERC-7677)

Point the SDK's paymaster URL at `https://api.liquidagent.ai/v1/gas`. `pm_getPaymasterStubData` is free.
An unpaid `pm_getPaymasterData` returns a JSON-RPC error `{code:402, data:<x402 PaymentRequired>}` with HTTP
200 (so SDKs don't treat it as a transport failure). Put the x402 payment object in `params[3].context.x402`
and retry; the result is the standard `{paymaster, paymasterData, paymasterVerificationGasLimit, paymasterPostOpGasLimit}`.
Confidence
81% confidence
Finding
Pointing an SDK paymaster URL at a third-party service means the wallet SDK may consume untrusted paymaster data and payment challenges over JSON-RPC. In this context, the endpoint can shape fee/payment prompts and returned paymaster fields, so weak client-side validation could cause users or agents to authorize unintended USDC payments or malformed sponsored operations.

Static analysis

No suspicious patterns detected.