T08 · Insecure Dependencies
- Location
SKILL.md:34- Finding
Unpinned Global Installation of a Mutable npm Dependency
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:34-39; duplicated inzyka-ai-media.md:13-18
Vulnerability Type: Unpinned third-party dependency installed globally
Risk Level: MediumVulnerable Code
SKILL.md:34-39:bash **Required: install the CLI once before using this skill.** All examples below assume `zyka` is on your PATH. ```bash npm install -g zyka # one-time install (latest) zyka --help # verify installtext Equivalent installation instructions appear in `zyka-ai-media.md`: ```bash Install the CLI once before using: ```bash npm install -g zyka # one-time install (latest) zyka --help # verify installtext ### Technical Analysis The Skill instructs users to install the mutable latest version of the `zyka` npm package globally. It does not pin the dependency to the reviewed Skill version, provide an integrity hash, use a lockfile, or require package signature or provenance verification. Because the executable implementation is not included in this repository, the security properties of the Skill depend on whatever package version npm resolves at installation time. Global npm installation may also run package lifecycle scripts and places the executable in a system-wide command path. A future compromised, malicious, or unexpectedly changed release could therefore execute code that was not present during this audit. This is a supply-chain weakness rather than evidence that the current package is malicious. The project identifies an official npm page and source repository, but those references do not make the installed artifact immutable. ### Attack Path 1. An attacker compromises the npm publisher account, package release process, or another component of the package supply chain. 2. The attacker publishes a malicious version under the legitimate `zyka` package name. 3. A user follows the Skill instructi ...[truncated 985 chars]- Remediation
View remediation
Remediation Suggestions
- Pin the CLI to an exact audited version, for example
npm install -g zyka@0.4.11, rather than installinglatest. - Ensure the pinned CLI version corresponds to the Skill documentation version.
- Publish and verify package integrity hashes, signatures, or npm provenance attestations.
- Prefer a project-local installation governed by a committed lockfile instead of global installation.
- Where compatible with the package, disable lifecycle scripts during installation and explicitly document any scripts that are required.
- Warn users not to run the installation with administrator or root privileges.
- Review the resolved package contents and dependency tree before updating the pinned version.
- Pin the CLI to an exact audited version, for example
