T08 · Insecure Dependencies
- Location
SKILL.md:73- Finding
Unpinned Third-Party MCP Package Executes with Wallet Credentials
- Content
View full analysis
- Remediation
View remediation
``` 2. Publish and verify expected package integrity hashes or signed release provenance. 3. Prefer installation through a lockfile-controlled project rather than retrieving a package dynamically on every launch. 4. Review and pin transitive dependencies using a package lockfile. 5. Remove automatic confirmation where practical so users can inspect the selected package and version. 6. Run the MCP server in an isolated environment with restricted filesystem and network access. 7. Use a dedicated seller wallet rather than a primary or high-value wallet. 8. Establish a key-rotation and incident-response procedure for package or registry compromise. ]]>
