T08 · Insecure Dependencies
- Location
SKILL.md:4- Finding
Unpinned Third-Party Executables Installed Without Integrity Verification
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 4 and 15–20
Vulnerability Type: Unverified and mutable third-party dependencies
Risk Level: MediumVulnerable Code
yaml metadata: {"clawdbot":{"emoji":"🚆","requires":{"bins":["trein"],"env":["NS_API_KEY"]},"primaryEnv":"NS_API_KEY","install":[{"id":"npm","kind":"node","package":"trein","bins":["trein"],"label":"Install trein (npm)"},{"id":"download-mac-arm","kind":"download","url":"https://github.com/joelkuijper/trein/releases/latest/download/trein-darwin-arm64","bins":["trein"],"label":"Download (macOS Apple Silicon)","os":["darwin"]},{"id":"download-mac-x64","kind":"download","url":"https://github.com/joelkuijper/trein/releases/latest/download/trein-darwin-x64","bins":["trein"],"label":"Download (macOS Intel)","os":["darwin"]},{"id":"download-linux","kind":"download","url":"https://github.com/joelkuijper/trein/releases/latest/download/trein-linux-x64","bins":["trein"],"label":"Download (Linux x64)","os":["linux"]}]}}markdown ## Install npm (recommended): ```bash npm i -g treinOr download a standalone binary from GitHub Releases.
text ### Technical Analysis The npm installation does not pin an audited package version or verify package integrity. The standalone installation options likewise use mutable `releases/latest/download/...` URLs and do not specify checksums or cryptographic signatures. Consequently, the executable installed by this Skill may change after the Skill itself has been reviewed. The package and repository names are consistent with the declared project homepage, and the audited file contains no direct evidence that the current upstream artifacts are malicious. Exploitation therefore depends on compromise of an upstream publisher, package, release, account, or delivery channel. ### Attack Path 1. An attacker compromises the npm package publisher, GitHub repos ...[truncated 1216 chars]- Remediation
View remediation
Remediation Suggestions
- Pin the npm dependency to a specific, reviewed version rather than installing the mutable latest release.
- Pin standalone downloads to explicit release versions instead of using
releases/latest. - Publish trusted SHA-256 or stronger checksums for every platform artifact and verify them before installation or execution.
- Prefer cryptographically signed releases and enforce signature verification against a documented maintainer key.
- Record the reviewed source revision and use reproducible builds where feasible.
- Run the CLI with least privilege and expose
NS_API_KEYonly to the specific process that requires it. - Establish a controlled update process that reviews new versions before changing the pinned version or expected digest.
