T08 · Insecure Dependencies
- Location
SKILL.md:56- Finding
Unpinned npm and npx Dependencies May Execute Unverified Registry Code
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 56–60 and 93–98
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumVulnerable Code
bash npm installbash npx vercel whoami npx vercel deploy dist --prod --yesTechnical Analysis
The documented workflow instructs users or agents to install npm dependencies and invoke the Vercel CLI without specifying an audited version. The reviewed artifact contains only
SKILL.md; it does not provide package metadata or a lockfile that would allow the installed dependency graph to be verified.npm installmay execute package lifecycle scripts from the resolved dependency graph. In addition, an unversionednpx vercelinvocation can download and execute the version currently selected by the npm registry when the CLI is not already available locally. This makes the effective executable code mutable after the skill has been reviewed.The deployment command also combines this dependency risk with a non-interactive production operation through
--prod --yes. Although production deployment is explicitly documented rather than hidden, executing a mutable CLI with existing Vercel credentials increases the potential impact of a compromised or unexpectedly changed package.Attack Path
- A user or agent follows the workflow in
SKILL.md. npm installresolves dependencies whose manifests and lockfile are not included in the reviewed artifact, ornpx vercelobtains an unpinned CLI release from the npm registry.- A compromised, substituted, or unexpectedly changed package executes through an npm lifecycle script or the CLI entry point.
- The package runs with the privileges and environment of the invoking account.
- It may access files, environment variables, npm configuration, or deployment credentials available to that account.
- In the deployment workflow, the package could alter deployment behavior or pub ...[truncated 832 chars]
- A user or agent follows the workflow in
- Remediation
View remediation
Remediation Suggestions
- Include the relevant
package.jsonand lockfile in the reviewable project package. - Replace
npm installwithnpm ciso installation is constrained to the committed lockfile. - Pin the Vercel CLI to an exact, audited version, for example:
bash npx --yes vercel@<audited-exact-version> whoami npx --yes vercel@<audited-exact-version> deploy dist --prod --yes - Prefer installing the pinned CLI as a development dependency and invoking it through a locked npm script.
- Review package lifecycle scripts and use
npm ci --ignore-scriptswhere lifecycle execution is unnecessary. - Verify registry configuration and package integrity before installation.
- Require explicit human confirmation immediately before any production deployment rather than presenting unattended production deployment as a routine command.
- Use narrowly scoped Vercel credentials and isolate deployment execution in a restricted CI environment without unrelated secrets.
- Validate the contents of
distand record the expected deployment target before invoking the production command.
- Include the relevant
