T08 · Insecure Dependencies
- Location
SKILL.md:10- Finding
Unpinned Global Installation of a Third-Party npm Package
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 10–14 and 56–59
Vulnerability Type: Unpinned third-party dependency installed globally
Risk Level: MediumVulnerable Code
yaml install: - kind: node package: ide-agent-kit bins: [ide-agent-kit]bash npm install -g ide-agent-kit ide-agent-kit init --ide claude-codeTechnical Analysis
The skill directs users to install
ide-agent-kitfrom the npm registry without specifying an exact version or integrity digest. It also recommends a global installation, making the resulting executable available throughout the user's environment.The reviewed project contains only
SKILL.md; it does not contain the package implementation, a lockfile, vendored source, or cryptographic integrity metadata. Consequently, the dependency's implementation and the document's security claims—including the absence of lifecycle scripts, localhost-only binding, credential handling, and command allowlisting—cannot be independently verified from the audited artifact.Because npm package resolution is mutable, the code installed later may differ from the code that existed when this skill was reviewed. A malicious release, compromised maintainer account, or registry/package takeover could therefore introduce unsafe behavior without requiring any change to
SKILL.md.Attack Path
- An attacker compromises the npm package, its publisher account, or its release pipeline.
- The attacker publishes a malicious release under the existing
ide-agent-kitpackage name. - A user follows the skill's instructions and runs
npm install -g ide-agent-kit. - npm resolves the current mutable release because no exact version or integrity digest is specified.
- The malicious package is installed with the privileges of the invoking user and exposes a global executable.
- When installation behavior or the executable is invoked, malicious code can access resources available to that user.
Impa
...[truncated 627 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to a reviewed, exact version rather than resolving the latest registry release.
- Record and verify a cryptographic integrity digest for the distributed package.
- Include a lockfile and use deterministic installation procedures such as
npm ciwhere applicable. - Avoid global installation; install the executable in an isolated, least-privileged project environment.
- Vendor or bundle the reviewed implementation so the executed code is identical to the audited code.
- Include the dependency source in future audit artifacts so its network, filesystem, credential, command-execution, webhook, and scheduling behavior can be validated.
- Inspect the package archive and lifecycle configuration before installation, and enforce installation policies that disable lifecycle scripts unless explicitly required and audited.
- Monitor the package publisher and release provenance, and require trusted signatures or equivalent supply-chain attestations before upgrades.
