T08 · Insecure Dependencies
- Location
SKILL.md:69- Finding
Unpinned Third-Party Packages Can Execute with Wallet-Signing Access
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is coherent for Ethereum launchpad work, but it asks users to use wallet-signing authority with unsafe transaction examples and unpinned external package execution that deserve review before installation.
Review this skill carefully before installing or using it with real funds. Use a dedicated low-value wallet, test on Sepolia first, pin and audit npm/MCP package versions, avoid giving a raw private key to an unpinned MCP process, explicitly set and validate your RPC URL, and replace every zero minimum-output transaction example with a quote-based slippage limit before signing.
SKILL.md:69Unpinned Third-Party Packages Can Execute with Wallet-Signing Access
SKILL.md:331Transaction Examples Disable Slippage Protection
SKILL.md:79Configured RPC Endpoint Is Ignored by Wallet and Public Client Examples
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Option A — IPFS via Pinata (recommended):
// POST image file to https://api.pinata.cloud/pinning/pinFileToIPFS
// POST metadata JSON to https://api.pinata.cloud/pinning/pinJSONToIPFS
// Headers: { Authorization: 'Bearer YOUR_PINATA_JWT' }
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Option A — IPFS via Pinata (recommended):
// POST image file to https://api.pinata.cloud/pinning/pinFileToIPFS
// POST metadata JSON to https://api.pinata.cloud/pinning/pinJSONToIPFS
// Headers: { Authorization: 'Bearer YOUR_PINATA_JWT' }
The swap examples set amountOutMin/minOut to 0n, which disables effective slippage protection and can expose users to severe price movement, MEV sandwiching, or unexpectedly poor execution. In a trading/deployment skill that encourages real mainnet interaction, presenting unsafe defaults without a strong inline warning materially increases loss risk.
No suspicious patterns detected.