T08 · Insecure Dependencies
- Location
SKILL.md:139- Finding
Unpinned npm Package Executes with Access to Wallet Credentials
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly upfront about being a paid Telegraph inference integration, but it grants automatic wallet-spending authority and a mutable remote tool surface with weak setup controls.
Install only with a strictly limited burner wallet, assume paid calls may spend USDC automatically, and avoid sending sensitive prompts or media unless you trust the Telegraph MCP package, its live registry, and the configured endpoints. Prefer a pinned package version, HTTPS endpoints, explicit spending limits, and confirmation before any paid call.
SKILL.md:139Unpinned npm Package Executes with Access to Wallet Credentials
SKILL.md:121Payment and Inference Operations Use Unencrypted Bare-IP HTTP Endpoints
SKILL.md:85Remote Registry Can Change the Available Tool Surface Without Local Approval
SKILL.md:121Paid Calls Sign Wallet Authorizations Without Agent-Visible Approval
The activation text is broad enough to trigger on very common user requests like weather, climate data, LLM completions, embeddings, image generation, or signal monitoring, even when the user did not specifically ask to use Telegraph. In this skill, activation can lead to paid tool use and external routing through a decentralized network, so over-broad triggering creates a real risk of unnecessary third-party disclosure and unintended spending.
The skill states that the MCP server handles x402 payments transparently and that the agent never sees the payment step, but the user-facing description does not make clear that ordinary inference requests may automatically sign and spend USDC from the configured wallet. Because many listed use cases are common assistant tasks, this can cause silent or surprising monetary loss if the skill activates without clear user consent.