T08 · Insecure Dependencies
Warning
- Location
SKILL.md:20- Finding
Unpinned Remote MCP Service Generates Security-Sensitive Payment Code
- Content
View full analysis
- Remediation
View remediation
Security audit
Crypto Payments Saas
Security checks for vulnerabilities and agentic risk
Overview
This payment skill is purpose-aligned, but it asks users to rely on a live remote service to generate sensitive billing, webhook, and payout code without enough scoping or security controls described.
Review this before installing. Treat all generated payment, webhook, payout, referral, and scaffolded code as untrusted until manually reviewed. Verify webhook signatures and payment state independently, make fulfillment idempotent, validate amounts and recipients, add audit logs, and require explicit approval for payouts or referral rewards. Avoid running project-assessment tools unless you understand what files and secrets the remote service can access.
Vulnerability Patterns
- Insecure DependenciesIntroduces malicious components through unsafe dependency sources
- 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)
Vulnerability Patterns
- Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
- Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
- 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
Findings (1)
Missing User Warnings
Medium
- Category
- Not specified by scanner
- Confidence
- 93% confidence
- Finding
The skill encourages use of webhook fulfillment, payouts, and referral automation that can directly change subscription state or move funds, but it does not warn users that these operations are security-sensitive and must be gated by strong verification and reconciliation. In a payments skill, omission of these warnings is dangerous because developers may copy the flow as-is and implement account activation, partner payouts, or billing changes based solely on incoming events, increasing the risk of fraudulent provisioning or unauthorized fund movement.
- Content