T08 · Insecure Dependencies
- Location
SKILL.md:66- Finding
Unpinned Third-Party Package Is Downloaded and Executed Through npx
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill openly connects an AI to many business apps, but the broad one-URL authority and unpinned npm command need review before installation.
Review this before installing. Connect only the apps and scopes you actually need, treat `BELLINK_URL` like a password, avoid pasting it into prompts or shell history, require approval for sends/bookings/writes, and prefer a pinned, reviewed package version if using the npm setup.
SKILL.md:66Unpinned Third-Party Package Is Downloaded and Executed Through npx
SKILL.md:66Authentication Key Is Embedded in a URL Passed Directly on the Command Line
The examples clearly show high-impact actions such as sending Gmail replies, booking appointments, creating spreadsheets, and creating project issues, but the skill does not prominently warn that connecting Bellink enables the AI to modify third-party services and send messages on the user's behalf. This can cause users to grant powerful access without informed consent, increasing the risk of unintended external actions, data modification, or business-impacting mistakes.
The skill instructs users to run npx bellink-mcp without pinning an exact package version, which allows whatever version is current on npm at execution time to run on the user's machine. If the package is compromised, republished maliciously, or a breaking change introduces unsafe behavior, users may execute unreviewed code with access to the Bellink URL credential and connected business data.
No suspicious patterns detected.