T08 · Insecure Dependencies
- Location
SKILL.md:114- Finding
Unpinned Global npm Dependency Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:114-116
Vulnerability Type: Unpinned third-party package installed globally
Risk Level: MediumVulnerable Code
bash npm install -g mcporterThe same installation instruction also appears in
README.md:20-23andREADME_zh.md:20-23.Technical Analysis
The installation command retrieves the current version of the
mcporterpackage without pinning an audited version or verifying its integrity or provenance. npm installations may execute package lifecycle scripts with the privileges of the invoking user. The global installation flag also makes the package available throughout the user's environment.The project does not provide a lockfile, package checksum, vendored source, signature-verification procedure, or another reproducibility mechanism for this dependency. Consequently, the code installed by this command may differ from the version assessed when the Skill was reviewed.
This is a supply-chain exposure rather than evidence that the current
mcporterpackage is malicious.Attack Path
- An attacker compromises the npm package, a maintainer account, or the relevant publication channel.
- The attacker publishes a malicious or backdoored release under the expected package name.
- A user follows the Skill's documented
npm install -g mcporterinstruction. - npm resolves and downloads the mutable current release rather than a previously reviewed version.
- Malicious package code or lifecycle scripts execute with the installing user's privileges.
- The globally installed CLI may subsequently execute attacker-controlled behavior whenever the Skill invokes
mcporter.
Impact Assessment
Successful exploitation could permit arbitrary code execution with the privileges of the user performing the installation. Depending on that user's permissions and environment, the malicious dependency could read or modify user-accessible files, access configuration or credentials, ...[truncated 305 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
mcporterto an exact, reviewed version instead of installing the mutable latest release. - Document the expected npm registry, package publisher, and reviewed package version.
- Verify package integrity and provenance through registry signatures, checksums, or equivalent controls before installation.
- Prefer a project-local dependency and lockfile over a global installation so dependency resolution is reproducible and constrained to the project.
- Review package lifecycle scripts and dependency trees before approving version updates.
- Apply automated dependency monitoring and require explicit security review before changing the pinned version.
- Keep the installation guidance consistent across
SKILL.md,README.md, andREADME_zh.md.
- Pin
