T08 · Insecure Dependencies
Warning
- Location
README.md:29- Finding
Unpinned Third-Party Installer and Skill Source
- Content
View full analysis
Vulnerability Details
File Location:
README.md:29-35
Vulnerability Type: Unpinned package execution and mutable supply-chain source
Risk Level: MediumVulnerable Code
markdown ## Installation ### Universal (Works with all platforms) ```bash npx skills add Abdullah4AI/mckinsey-researchtext ### Technical Analysis The documented installation procedure invokes the third-party `skills` npm package through `npx` without specifying an exact package version or integrity digest. Depending on the local npm configuration and cache state, `npx` can retrieve and execute the package version currently resolved by the registry. The Skill source is also identified by a mutable GitHub repository reference rather than a reviewed commit hash or signed release. Consequently, both the installer behavior and installed Skill content may change after this audit without any corresponding change to the reviewed artifact. No evidence indicates that the currently reviewed project or documented package is malicious. The vulnerability is the absence of immutable dependency and source pinning, which creates a supply-chain attack opportunity. ### Attack Path 1. An attacker compromises the npm package, its publisher account, the package registry resolution path, or the referenced GitHub repository. 2. The attacker publishes malicious installer code or modifies the repository content referenced by the installation command. 3. A user follows the documented `npx skills add Abdullah4AI/mckinsey-research` instruction. 4. `npx` resolves and executes the altered installer package, which then obtains the mutable Skill source. 5. Malicious code executes with the privileges of the user running the installation command or malicious Skill instructions are installed into the user's agent environment. ### Impact Assessment Successful exploitation could execute arbitrary code with the installing user's privileges. This may permit access to files, credentials, environmen ...[truncated 420 chars]- Remediation
View remediation
Remediation Suggestions
- Pin the
skillsnpm package to an exact reviewed version rather than allowing registry resolution to select the current release. - Use a lockfile and npm integrity metadata wherever the installation workflow supports them.
- Pin the Skill source to a reviewed Git commit hash or immutable signed release tag.
- Publish and verify release checksums or cryptographic signatures before installation.
- Avoid running the installation command with administrative privileges.
- Document the expected package publisher, repository owner, commit hash, and verification procedure.
- Add automated dependency and provenance checks to detect package ownership changes, unexpected release modifications, and integrity mismatches.
- Prefer an installation mechanism that downloads verified content without executing a mutable package during installation.
- Pin the