T08 · Insecure Dependencies
- Location
README.md:62- Finding
Unpinned Third-Party Package Execution During Installation
- Content
View full analysis
Vulnerability Details
File Location:
README.md:62
Vulnerability Type: Supply-chain exposure through an unpinned executable dependency
Risk Level: MediumVulnerable Code:
bash npx skills add alchaincyf/system-awakeningTechnical Analysis
The documented installation command uses
npxto retrieve and execute theskillsnpm package without specifying an audited version. The requested Skill repository or package revision is also not pinned to an immutable commit or release.Consequently, the code executed by this command can differ from the code that was examined during this audit. If the npm package, publishing account, package registry, or referenced Skill repository is compromised, a later installation can execute attacker-controlled behavior. No evidence of an existing compromise or malicious payload was identified in the audited files; the issue is the unsafe and mutable dependency trust model.
Attack Path
- An attacker compromises the npm package, its maintainer account, the package registry path, or the referenced Skill distribution source.
- The attacker publishes a modified release under the same mutable package identity.
- A user follows the documented installation procedure and runs the unpinned
npxcommand. npxdownloads and executes the currently resolved package version rather than a previously audited version.- The malicious installer runs with the privileges and environment of the invoking user.
Impact Assessment
Successful exploitation could permit arbitrary code execution with the installing user's privileges. Depending on that user's access, the payload could read or modify user files, access credentials available to the process, alter development configuration, install additional components, or modify local Skill files.
The issue does not directly provide administrative privileges unless the command is run from an elevated account. Its scope is ...[truncated 115 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the npm CLI to a specific audited version, for example by using an exact package version rather than the latest registry resolution.
- Pin the installed Skill to an immutable commit hash or cryptographically identified release instead of a mutable repository reference.
- Publish SHA-256 checksums or signed release attestations and document how users can verify downloaded artifacts before installation.
- Prefer a two-step installation process that downloads and verifies the package before executing any installer logic.
- Use npm lockfiles and integrity metadata wherever the installation mechanism supports them.
- Document that users should not run the installer with administrative privileges.
- Add automated dependency monitoring and require maintainer account protections such as multi-factor authentication and provenance-enabled publishing.