Back to skill

Security audit

scout-packs

Security checks for vulnerabilities and agentic risk

Overview

This is a disclosed pay-per-call contact lookup skill, but it tells agents to make real USDC payments and send company queries without a clear per-transaction user approval gate.

Review before installing. Use this only when you intentionally want paid B2B contact enrichment, and require confirmation before each lookup showing the company query, $0.01 USDC amount, Base network, USDC contract, recipient address, and cumulative spend. Do not use it for confidential prospect lists unless you are comfortable sending those company names or domains to the vendor.

Vulnerability Patterns
  • 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
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T09 · Insecure Skill Coding Practices

Warning
Location
SKILL.md:43
Finding

Payment Workflow Lacks Transaction-Specific User Confirmation

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 43–59
Vulnerability Type: Financial transaction without an explicit confirmation gate
Risk Level: Medium

Vulnerable Snippet

markdown
**Step 1 — Request the lookup.** An unpaid request returns HTTP 402 with the
exact payment terms:

```bash
curl -s "https://scout-packs-production.up.railway.app/lookup?query=<company name or domain>"

The 402 response tells you exactly what to pay: $0.01 USDC on Base to the payTo address shown (USDC contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, amount 10000 base units). Always use the payTo address from the live 402 response, never a cached one.

If the company isn't in the index you get a 404 with suggestions instead — no payment needed. Only pay when the 402 challenge confirms your query matched.

Step 2 — Pay from a wallet you control. Send exactly $0.01 USDC on Base to the payTo address and wait for confirmation. Standard x402 agents may instead sign an EIP-3009 authorization and retry with the signature in the X-PAYMENT (v1) / PAYMENT-SIGNATURE (v2) header — the payment is verified and settled by facilitator, no separate transfer needed.

text

### Technical Analysis

The documented workflow directs an agent to perform an irreversible cryptocurrency payment, or sign an EIP-3009 payment authorization, immediately after receiving an HTTP 402 response. It does not require transaction-specific approval from the user after presenting the final query, amount, token, network, and recipient.

The remote service controls the live HTTP 402 response and therefore supplies the `payTo` address used by the agent. Although the document states that the payment should be exactly $0.01 USDC on Base, it provides no enforced approval gate or executable validation mechanism. The instructions also encourage agents to use the live recipient rather than a previously reviewed recipient.

...[truncated 1333 chars]
Remediation
View remediation

Remediation Suggestions

  1. Require explicit user confirmation immediately before every payment or signed payment authorization.
  2. Display the exact lookup query, amount, token contract, network, recipient address, and cumulative session spend in the confirmation prompt.
  3. Reject any HTTP 402 challenge whose amount, token contract, or chain differs from the documented values.
  4. Enforce a hard maximum of $0.01 USDC per lookup rather than relying only on prose instructions.
  5. Add configurable per-session call and spending limits, with additional confirmation before exceeding them.
  6. Default batch enrichment to a quote or dry-run mode that reports expected costs before initiating any transaction.
  7. Ensure cancellation or ambiguous user responses cannot be interpreted as payment authorization.
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (3)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The description advertises 'no API key, no account, no subscription' and mentions the $0.01 fee, but it does not present a prominent user-facing warning that each successful lookup causes a real USDC payment on Base. In agent settings, brief descriptions are often what governs tool selection, so an understated payment warning can lead to autonomous or accidental spending of user funds.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

The invocation guidance is broad enough that an agent could select this skill for ordinary prospecting, enrichment, or research tasks without a strong gating condition or explicit requirement for user approval before spending funds. Because each invocation can trigger a real blockchain payment and external disclosure of company queries, loose triggering increases the chance of unintended paid actions and unnecessary data transmission.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
88% confidence
Finding

The skill instructs the agent to send company names or domains to a third-party service, which is an external transmission of potentially sensitive user or business data. In this context the transmission is core to the service, but it is still risky because prospect lists, target companies, or research interests may be confidential and are disclosed to the vendor before fulfillment.

Content

Scanner excerpt · SKILL.md (reported line 47)May include surrounding context.

exact payment terms:

bash
curl -s "https://scout-packs-production.up.railway.app/lookup?query=<company name or domain>"

The 402 response tells you exactly what to pay: $0.01 USDC on Base to the