T08 · Insecure Dependencies
- Location
SKILL.md:24- Finding
Unpinned Third-Party Package Execution with Bootstrap Credential Access
- Content
View full analysis
--gateway ` 5. Let `hipokamp-mcp` write local config under `~/.hipokamp/config.json`. ``` ### Technical Analysis The documented command invokes `hipokamp-mcp` through `npx` without pinning an exact package version or requiring integrity or signature verification. Depending on the local npm configuration and cache, `npx` may retrieve the package from a remote registry and immediately execute its installation or runtime code with the invoking user's privileges. The package receives a sensitive bootstrap token through a command-line argument and is expected to write configuration beneath the user's home directory. Consequently, a compromised, replaced, or incorrectly identified npm package would have both local code-execution capability and direct access to an authentication credential. The package name `hipokamp-mcp` also differs in spelling from the “Hippocampus” product name used throughout the document. The available project material does not establish that this name is malicious or incorrect, but the discrepancy increases package-identity and typo-squatting uncertainty. No malicious behavior in the package itself can be confirmed because its source is not included in the audited project. ### Attack Path 1. An attacker compromises the npm account or release process for `hipokamp-mcp`, or publishes a confusingly named package that users resolve instead of the intended package. 2. The user follows the onboarding instructions and runs the unpinned `npx hipokamp-mcp` command. 3. `npx` retrieves the mutable package version currently selected by the configured registry. 4. npm executes package-controlled installation or runtime code with the permissions of th ...[truncated 951 chars]- Remediation
View remediation
