Back to skill

Security audit

Wip Agent Pay Private

Security checks for vulnerabilities and agentic risk

Overview

This payment skill is coherent with its stated wallet purpose, but it gives agents broad spending and wallet authority with weak scoping and several unsafe implementation details.

Review carefully before installing. Use only an isolated, low-balance wallet, avoid broad shared worker secrets, require explicit approval and hard spend caps for every payment, and do not run the CLI against untrusted worker responses until the URL validation, shell execution, budget enforcement, and signing-scope issues are fixed.

Vulnerability Patterns
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • 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
Findings (6)

T05 · Unauthorized Access and Privilege Escalation

Error
Location
providers/index.js:19
Finding

Shared Bearer Secret Grants Unrestricted Access to Privileged Wallet Operations

Content
View full analysis
Remediation
View remediation

T05 · Unauthorized Access and Privilege Escalation

Error
Location
worker/index.js:190
Finding

Untrusted Paywall Responses Directly Control Server-Wallet Signatures

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Error
Location
worker/index.js:975
Finding

Configured Spending Limits Are Not Enforced Before Payment Signing

Content
View full analysis
budget.perTx) { return { allowed: false, reason: `Exceeds per-transaction limit of $${budget.perTx}` }; } // Daily limit if (budget.daily) { const ledgerKey = `ledger:${wallet}`; const ledgerData = await env.PAY_LEDGER?.get(ledgerKey); if (ledgerData) { const ledger = JSON.parse(ledgerData); const todayStart = new Date(); todayStart.setHours(0, 0, 0, 0); const todayMs = todayStart.getTime(); const spentToday = ledger .filter(tx => tx.timestamp >= todayMs && tx.type !== 'fund') .reduce((sum, tx) => sum + (parseFloat(tx.amount) || 0), 0); if (spentToday + parseFloat(amount) > budget.daily) { return { allowed: false, reason: `Would exceed daily limit of $${budget.daily} (spent: $${spentToday.toFixed(2)})` }; } } } return { allowed: true }; } ``` ### Technical Analysis The project defines a budget-enforcement function, but the audit found no invocation of `checkBudget`. Direct CDP payments, Privy payments, pool payments, and user-wallet payments proceed to signing without consulting configured daily or per-transaction limits. This creates a security-control mismatch: users can set and view budget values, and the documentation presents spending limits as part of the security model, but the payment paths do not enforce them. A simple call would still be insufficient under concurrency because checking a ledger and later recording a transaction ...[truncated 843 chars]
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Error
Location
worker/index.js:190
Finding

Arbitrary Worker-Side URL Fetching Enables SSRF and Response Disclosure

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Error
Location
cli.js:88
Finding

Remote Checkout URL Is Interpolated into a Shell Command

Content
View full analysis
"`. 5. `execSync` invokes a shell to interpret the complete string. 6. The injected command executes with the privileges of the user running `wip-pay`. ### Impact Assessment Successful exploitation provides arbitrary command execution und ...[truncated 241 chars]
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Error
Location
ai/test-skills/Morning-Stew-skill.md:32
Finding

Packaged Test Skill Stores Funded Wallet Private Keys in Plaintext Files

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • 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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Rogue AgentSelf-Modification, Session Persistence
Findings (116)

Tp4

High
Category
MCP Tool Poisoning
Confidence
97% confidence
Finding

Retrieving a worker secret from 1Password or environment, checking balances, viewing transaction history, managing budgets, and minting one-time payment URLs are all sensitive financial operations that materially exceed the simple marketing description. In this context, the mismatch is dangerous because it conceals surveillance and control over wallet activity and could enable unauthorized spending or exposure of private financial metadata.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
97% confidence
Finding

Retrieving a worker secret from 1Password or environment, checking balances, viewing transaction history, managing budgets, and minting one-time payment URLs are all sensitive financial operations that materially exceed the simple marketing description. In this context, the mismatch is dangerous because it conceals surveillance and control over wallet activity and could enable unauthorized spending or exposure of private financial metadata.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
97% confidence
Finding

Retrieving a worker secret from 1Password or environment, checking balances, viewing transaction history, managing budgets, and minting one-time payment URLs are all sensitive financial operations that materially exceed the simple marketing description. In this context, the mismatch is dangerous because it conceals surveillance and control over wallet activity and could enable unauthorized spending or exposure of private financial metadata.

Content

No source excerpt is available for this finding.

Tp4

High
Category
MCP Tool Poisoning
Confidence
97% confidence
Finding

Retrieving a worker secret from 1Password or environment, checking balances, viewing transaction history, managing budgets, and minting one-time payment URLs are all sensitive financial operations that materially exceed the simple marketing description. In this context, the mismatch is dangerous because it conceals surveillance and control over wallet activity and could enable unauthorized spending or exposure of private financial metadata.

Content

No source excerpt is available for this finding.

Missing User Warnings

High
Category
Not specified by scanner
Confidence
97% confidence
Finding

The document explicitly promotes an agent signing blockchain payments from the user's wallet with 'no approval popup' and 'no human in the loop,' but it does not present a prominent warning about the financial risk, spending authority, or consequences of autonomous payment execution. In a wallet/payment skill, omission of a clear consent and risk warning is dangerous because users may enable persistent spending authority without understanding that the agent can authorize irreversible on-chain transfers.

Content

No source excerpt is available for this finding.

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · ai/dev-update/2026-02-23.md (reported line 123)May include surrounding context.

md
Because agents operate in text. They can't set HTTP headers in most UIs. A URL is universal. Paste it. Click it. Done. And it dies after one use so there's nothing to steal.

**Why 1Password, not env vars?**
Because Parker's architecture is 1Password-native. SA token, no .env files, no credentials on disk. The agent proves authority through 1Password every time.

**Why atomic delete instead of mark-used?**
Two simultaneous requests could both read "used: false" before either writes "used: true". Delete-on-read means first reader wins. Second reader gets 410. No double-spend.

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · ai/dev-update/dev-update-2026-02-23--09-38-00.md (reported line 123)May include surrounding context.

md
Because agents operate in text. They can't set HTTP headers in most UIs. A URL is universal. Paste it. Click it. Done. And it dies after one use so there's nothing to steal.

**Why 1Password, not env vars?**
Because Parker's architecture is 1Password-native. SA token, no .env files, no credentials on disk. The agent proves authority through 1Password every time.

**Why atomic delete instead of mark-used?**
Two simultaneous requests could both read "used: false" before either writes "used: true". Delete-on-read means first reader wins. Second reader gets 410. No double-spend.

Description-Behavior Mismatch

High
Category
Not specified by scanner
Confidence
96% confidence
Finding

The manifest says the skill gives an agent a wallet and funds it with Apple Pay, implying wallet-oriented payment functionality. This file instead explicitly states 'AGENT CASH is: Not a wallet' and reframes the system as a curated micro-transaction unlock network, which is a direct semantic mismatch with the skill's declared purpose.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

High
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill manifest claims wallet capabilities ('Give your agent a wallet'), while the file's strategic positioning section expressly denies that characterization. Because this is affirmative documentation that contradicts the stated skill intent, it is an intent-code/documentation divergence rather than mere incompleteness.

Content

No source excerpt is available for this finding.

Self-Modification

High
Category
Rogue Agent
Confidence
85% confidence
Finding

Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.

Content

Scanner excerpt · ai/plans/three-providers--2026-02-23.md (reported line 506)May include surrounding context.

md
33. Update SPEC.md (three providers, provider selection)
34. Update SETUP.md (three setup paths)
35. Update SKILL.md
36. Update README.md
37. Dev update
38. Tag release

Missing User Warnings

High
Category
Not specified by scanner
Confidence
97% confidence
Finding

The skill explicitly instructs users or agents to generate a wallet and write the private key to a local JSON file. Persisting hot-wallet credentials in plaintext materially increases the chance of theft via local compromise, logs, backups, workspace sharing, or downstream tools that read the filesystem. In this context, the skill is payment-focused, so the key directly controls funds, which makes the risk more serious rather than incidental.

Content

No source excerpt is available for this finding.

Known Vulnerable Dependency: @hono/node-server==1.19.9 — 3 advisory(ies): CVE-2026-39406 (@hono/node-server: Middleware bypass via repeated slashes in serveStatic); GHSA-frvp-7c67-39w9 (Node.js Adapter for Hono: Path traversal in `serve-static` on Windows via encode); CVE-2026-29087 (@hono/node-server has authorization bypass for protected static paths via encode)

High
Category
Supply Chain
Confidence
95% confidence
Finding

@hono/node-server 1.19.9 is flagged for multiple high-severity issues affecting static file serving, including path traversal and authorization or middleware bypasses. In a payment-enabled agent skill, any reachable local web endpoint or callback server increases the risk that protected files, tokens, or wallet-related data could be exposed or access controls bypassed.

Content

No source excerpt is available for this finding.

Known Vulnerable Dependency: express-rate-limit==8.2.1 — 1 advisory(ies): CVE-2026-30827 (express-rate-limit: IPv4-mapped IPv6 addresses bypass per-client rate limiting o)

High
Category
Supply Chain
Confidence
94% confidence
Finding

express-rate-limit 8.2.1 is flagged for bypass via IPv4-mapped IPv6 addresses, which can let an attacker evade per-client throttling. For a wallet and payment-related agent, rate-limit bypass materially increases abuse risk such as brute-force attempts, transaction flooding, or enumeration of protected endpoints.

Content

No source excerpt is available for this finding.

Known Vulnerable Dependency: fast-uri==3.1.0 — 7 advisory(ies): CVE-2026-13676 (fast-uri vulnerable to host confusion via failed IDN canonicalization); CVE-2026-18446 (fast-uri vulnerable to host confusion via backslash authority introducer); CVE-2026-75975 (fast-uri vulnerable to server-side request forgery via malformed IPv6 normalizat) +4 more

High
Category
Supply Chain
Confidence
90% confidence
Finding

fast-uri 3.1.0 is associated with several high-severity URI parsing flaws, including host confusion and possible SSRF-enabling edge cases. In a skill that may fetch paywalled content or interact with remote payment infrastructure, incorrect URI canonicalization can cause requests to be sent to unintended hosts or bypass host validation logic.

Content

No source excerpt is available for this finding.

Known Vulnerable Dependency: hono==4.12.2 — 16 advisory(ies): CVE-2026-56762 (Hono missing validation of cookie name on write path in setCookie()); CVE-2026-47676 (Hono: app.mount() strips mount prefix using undecoded path, causing incorrect ro); CVE-2026-47675 (Hono: Cookie helper does not sanitize sameSite and priority, allowing Set-Cookie) +13 more

High
Category
Supply Chain
Confidence
96% confidence
Finding

hono 4.12.2 is flagged for numerous high-severity issues spanning cookies, routing, and path handling. Because this skill's purpose involves payments and likely web-facing interactions, weaknesses in request routing, cookie handling, or static path protection can directly undermine auth boundaries and expose sensitive financial or session data.

Content

No source excerpt is available for this finding.

Known Vulnerable Dependency: ip-address==10.0.1 — 2 advisory(ies): CVE-2026-69192 (ip-address: Address4 decodes leading-zero octets as decimal while resolvers deco); CVE-2026-42338 (ip-address has XSS in Address6 HTML-emitting methods)

High
Category
Supply Chain
Confidence
84% confidence
Finding

ip-address 10.0.1 is reported vulnerable to parsing inconsistencies and XSS in HTML-emitting methods. The host parsing issue is more relevant here: if this library participates in client IP handling for rate limiting or network validation, ambiguous address interpretation can help attackers bypass security controls.

Content

No source excerpt is available for this finding.

Known Vulnerable Dependency: path-to-regexp==8.3.0 — 2 advisory(ies): CVE-2026-4923 (path-to-regexp vulnerable to Regular Expression Denial of Service via multiple w); CVE-2026-4926 (path-to-regexp vulnerable to Denial of Service via sequential optional groups)

High
Category
Supply Chain
Confidence
89% confidence
Finding

path-to-regexp 8.3.0 is flagged for ReDoS issues caused by crafted route patterns or pathological matching behavior. If exposed HTTP endpoints use affected routing logic, an attacker may be able to consume CPU and degrade availability, which is particularly concerning for a payment-capable service where reliability and abuse resistance are important.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

High
Category
Not specified by scanner
Confidence
97% confidence
Finding

The file explicitly states that the worker mints real one-time payment URLs while no Coinbase transfer occurs yet. In a payment skill, this creates a dangerous mismatch between advertised behavior and actual settlement, which can cause users or downstream agents to assume funds were sent when they were not. Because the component still returns success and a payment URL, it can enable unpaid access, accounting errors, or unauthorized consumption of paywalled resources.

Content

No source excerpt is available for this finding.

Missing User Warnings

High
Category
Not specified by scanner
Confidence
95% confidence
Finding

The skill explicitly describes autonomous payment authorization, retrieval of credentials from 1Password, and transfer of USDC from an isolated portfolio without disclosing any mandatory user confirmation, approval boundary, or safety interlock. In a finance/payment skill, this is especially dangerous because it normalizes delegated spending and secret access by an agent, which could enable unauthorized purchases or abuse if invoked unexpectedly or by prompt injection.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The content promotes AI-mediated purchasing with frictionless approval language like 'You say "let's go"' and 'Done' but does not present any explicit warning about financial risk, merchant trust, refundability, recurring charges, or the need for careful user confirmation. In a skill whose core purpose is enabling payments, omission of spending-risk guidance can normalize impulsive or insufficiently informed transactions and increase the chance of unauthorized or deceptive purchases.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

The deployment guide has users publish a public endpoint where possession of the tokenized URL is sufficient to retrieve stored payment metadata and irreversibly consume the token. Because the URL itself is the bearer secret and the guide does not clearly warn about sharing, logging, referrer leakage, or accidental exposure, users may unintentionally leak tokens and lose access or disclose associated payment details.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
98% confidence
Finding

The code claims token consumption is atomic and race-free, but it performs a separate KV get followed by KV delete. In Cloudflare KV, these are distinct operations without transactional guarantees, so concurrent requests can both read the token before either delete completes, allowing multiple successful consumptions of what is intended to be a one-time payment token.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

The suggested prompt 'I want to become an AI CASH partner store. Walk me through the process.' is natural conversational language and the file does not define explicit activation boundaries, exclusions, or narrower trigger phrases. In a markdown skill description, this can create ambiguity about when an agent should treat similar everyday phrasing as invoking this partner-onboarding workflow.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
92% confidence
Finding

The README encourages agent-mediated payments and content unlocking while emphasizing convenience ('no setup', 'just say let’s go') but does not prominently warn about transaction risk, third-party payment processing, or the need for explicit user consent boundaries. In a skill whose core purpose is spending money and redeeming access tokens, under-documenting financial risk can lead users to authorize unintended purchases or misunderstand who handles funds and what trust assumptions they are accepting.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The documentation explicitly tells users to store Coinbase API credentials and the worker secret in 1Password, and elsewhere states the skill will routinely pull and use those secrets. Failing to clearly warn users that normal invocation causes secret retrieval and use can lead to users enabling powerful financial credentials without informed consent, increasing the risk of unintended transfers or secret exposure through downstream tooling.

Content

No source excerpt is available for this finding.