Back to skill

Security audit

skill-by-test

Security checks for vulnerabilities and agentic risk

Overview

This sandbox payment-link skill is not malicious, but its helper script sends unvalidated payment data to a local HTTP API and does not actually use the declared API key.

Use this only for local sandbox testing. Do not provide production API keys, real cardholder data, real customer data, or live webhook endpoints. Before any production use, require schema validation, remove the hard-coded placeholder key, use the declared environment secret correctly, authenticate requests, and move payment traffic to an authenticated HTTPS or otherwise secured local channel.

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 (3)

T09 · Insecure Skill Coding Practices

Note
Location
scripts/test-scrpt.js:1
Finding

Hard-Coded and Ineffective API Credential Handling

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Note
Location
scripts/test-scrpt.js:3
Finding

Payment API Requests Use Unencrypted HTTP Transport

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
scripts/test-scrpt.js:42
Finding

Unvalidated Arbitrary Fields Are Forwarded to the Payment API

Content
View full analysis
0 ? JSON.stringify(rest) : undefined; } async function main() { const raw = process.argv[2]; if (!raw) throw new Error("No payload provided. Pass JSON as first argument."); const { type, data } = JSON.parse(raw); if (!type) throw new Error("Missing 'type' in payload."); const endpoint = ENDPOINTS[type]; if (!endpoint) throw new Error(`Unsupported type: "${type}"`); const { method, path } = endpoint; const resolvedPath = buildUrl(path, data); const queryString = method === "GET" ? buildQueryString(type, data) : ""; const url = `${BASE}${resolvedPath}${queryString}`; const body = method !== "GET" ? buildBody(type, data) : undefined; const res = await fetch(url, { method, headers: { "Content-Type": "application/json", }, ...(body ? { body } : {}), }); ``` ### Technical Analysis The script parses attacker-controllable command-line JSON and verifies only that a supported `type` is present. For the supported POST operation, `buildBody` removes the `id` property but serializes every other supplied property without an allowlist or schema validation. The implementation does not enforce the validation controls described in `SKILL.md`, including positive numeric amounts, ISO currency codes, URL format, email format, metadata structure, duplicate-product prevention, or sanitization. It also does not limit payload depth or size. This creates a validation-boundary failure: the Skill presents itself as the component responsible for validating payment-link inputs but delegates arbitrary object ...[truncated 1652 chars]
Remediation
View remediation
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)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

This skill is centered on payment-link creation, webhook handling, and API-driven network operations, but it does not present a prominent user-facing warning about sensitive payment-related data, external requests, and the risk of exposing secrets or interacting with financial workflows. In this context, missing warnings can lead users or downstream agents to provide sensitive data unsafely, mis-handle webhook endpoints, or assume the skill is safer than it is, increasing the chance of credential leakage or unintended financial actions.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

This code performs a network POST request and may transmit arbitrary fields from the user-supplied data object, but there is no confirmation prompt, warning message, or explanatory comment disclosing that payload data will be sent over HTTP. The only visible output is the response after the request completes, which does not warn the user beforehand about data transmission.

Content

No source excerpt is available for this finding.