T09 · Insecure Skill Coding Practices
- Location
scripts/test-scrpt.js:1- Finding
Hard-Coded and Ineffective API Credential Handling
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
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.
scripts/test-scrpt.js:1Hard-Coded and Ineffective API Credential Handling
scripts/test-scrpt.js:3Payment API Requests Use Unencrypted HTTP Transport
scripts/test-scrpt.js:42Unvalidated Arbitrary Fields Are Forwarded to the Payment API
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.
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.