T08 · Insecure Dependencies
- Location
README.md:19- Finding
Unpinned npm Package Is Downloaded and Executed During Installation
- Content
View full analysis
Vulnerability Details
File Location:
README.md:19
Vulnerability Type: Unpinned third-party package execution
Risk Level: MediumComplete Code Snippet:
bash npx skills add alexpolonsky/agent-skill-libby-book-monitorTechnical Analysis
The recommended installation command invokes the
skillsnpm package throughnpxwithout specifying an exact version or integrity value. If the package is not already available locally,npxcan retrieve it from the configured npm registry and immediately execute its command.Consequently, the code executed during installation is not fully represented by, or immutable with respect to, the audited project. A future package update, registry-account compromise, package takeover, or compromised dependency could alter installation behavior after this Skill has been reviewed. This is a supply-chain exposure rather than evidence that the current
skillspackage is malicious.Attack Path
- An attacker compromises the npm package, its publisher account, or a dependency used by the package that provides the
skillscommand. - The attacker publishes a modified version containing malicious installation or runtime behavior.
- A user follows the documented unpinned
npx skills add ...command. npxresolves and downloads the mutable package version from the configured registry.- The downloaded package executes with the privileges of the user running the installation command.
- Malicious code could then access, alter, or exfiltrate resources available to that user.
Impact Assessment
Successful exploitation could provide arbitrary code execution under the installing user's account. The accessible scope could include that user's files, environment variables, agent configuration, developer credentials, and network permissions. It would not inherently grant administrator or root privileges unless the command were run with elevated privileges or anoth ...[truncated 298 chars]
- An attacker compromises the npm package, its publisher account, or a dependency used by the package that provides the
- Remediation
View remediation
Remediation Suggestions
- Pin the installer package to an exact reviewed version:
bash npx skills@<exact-reviewed-version> add alexpolonsky/agent-skill-libby-book-monitor - Avoid floating tags such as
latest, version ranges, or unspecified versions. - Document the expected package publisher, registry, version, and integrity information so users can verify the retrieved artifact.
- Prefer installation from a reviewed repository tag or commit hash where practical, and document commit verification.
- Recommend running installation without administrator privileges and in an isolated environment when possible.
- Periodically review and update the pinned version only after auditing the package and its dependency changes.
- Pin the installer package to an exact reviewed version:
