T08 · Insecure Dependencies
- Location
SKILL.md:16- Finding
Unpinned Third-Party Package Installed Globally
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 16-25 and line 36
Vulnerability Type: Unpinned and unaudited third-party dependency
Risk Level: MediumVulnerable Code
yaml "install": [ { "id": "npm", "kind": "node", "package": "@shan8851/rail-cli", "bins": ["rail"], "label": "Install rail-cli (npm)", }, ],markdown - `npm install -g @shan8851/rail-cli`Technical Analysis
The Skill instructs users to install
@shan8851/rail-cliglobally without specifying an exact version or integrity value. Consequently, installation resolves whichever package version the npm registry currently serves rather than an immutable, previously audited artifact.A global npm installation can execute package lifecycle scripts during installation and place the package's
railexecutable in the user's global command path. The audited project does not contain the dependency's source, lockfile, integrity hash, or publisher-verification information, so the executable behavior cannot be validated from this artifact.There is no evidence in
SKILL.mdthat the named package is currently malicious. The vulnerability arises from trusting a mutable, externally maintained package without version or integrity controls.Attack Path
- An attacker compromises the package publisher's npm account, the package itself, or one of its transitive dependencies.
- The attacker publishes a malicious version under the existing package name.
- A user follows the Skill's documented command:
npm install -g @shan8851/rail-cli. - npm resolves and downloads the malicious current release because no exact version is pinned.
- Malicious lifecycle code can execute during installation, or malicious logic can run when the globally installed
railcommand is invoked. - The code executes with the installing user's privileges and may access that user's files, ...[truncated 874 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the package to an exact reviewed version, for example
@shan8851/rail-cli@X.Y.Z, rather than resolving the latest release. - Record and verify the expected package integrity hash before installation.
- Prefer a project-local installation backed by a committed lockfile over
npm install -g. - Include or link to the exact auditable source revision corresponding to the pinned package release.
- Verify npm publisher ownership, package provenance, release signatures, and registry metadata.
- Review the package and its transitive dependencies for lifecycle scripts before deployment.
- Where compatible with the package, install with lifecycle scripts disabled and enable only explicitly reviewed setup operations.
- Run the CLI with least privilege and expose
DARWIN_ACCESS_TOKENonly to the specific process that requires it. - Add automated dependency monitoring so that upgrades require review rather than silently changing the installed implementation.
- Pin the package to an exact reviewed version, for example
