T09 · Insecure Skill Coding Practices
- Location
SKILL.md:66- Finding
Shell Command Injection Through User-Controlled Payment Fields
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly coherent for creating Shieldz payment links, but its shell examples and optional local MCP package create review-worthy execution risks.
Review before installing. Use the REST flow with a structured HTTP client or safe JSON serialization, keep manage_url and manage_token private, and avoid the optional local npx MCP path unless you trust and sandbox that package. Be comfortable sending wallet address, amount, memo/title, optional email, and manage tokens to Shieldz.
SKILL.md:66Shell Command Injection Through User-Controlled Payment Fields
SKILL.md:107Unverified Third-Party Package Download and Execution Through npx
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- an **email address**, only if the user explicitly provides one (see below)
- when reading status, the **manage_token**
Treat every `manage_url` / `manage_token` as a **private access credential**:
anyone holding it can read the account's totals and settings. Do not post them
publicly, paste them into shared contexts, or write them to logs.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Keyless, no Authorization header. Only call this after the confirmation above.
curl https://shieldz.cash/api/v1/links \
-H "Content-Type: application/json" \
-d '{
"settlement": { "chain": "BASE", "asset": "USDC", "address": "0xUserProvidedWallet" },
No suspicious patterns detected.