T08 · Insecure Dependencies
- Location
SKILL.md:253- Finding
Unpinned Third-Party Installation Command Creates a Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:253
Vulnerability Type: Unpinned third-party dependency and mutable remote source
Risk Level: MediumVulnerable Code
text npx skills add WardLu/skills --skill codex-cross-provider-session-repair --global --agent codex --yesTechnical Analysis
The documented installation command invokes the
skillsnpm package without specifying a package version. It also installs Skill content from the mutableWardLu/skillsGitHub repository without pinning a commit hash or verifying an archive checksum or signature.As a result, the code installed by this command can differ from the artifact covered by this audit. The
--yesoption further suppresses interactive confirmation. This creates a supply-chain trust boundary involving both the npm package and the remote repository.The audited project itself does not retrieve or execute a remote payload during its normal repair workflow. The risk is specifically associated with the documented installation command.
Attack Path
- An attacker compromises the npm package, its publishing credentials, the referenced GitHub repository, or a relevant upstream account.
- The attacker publishes a modified package version or changes the repository content.
- A user executes the documented unpinned
npx skills add ... --yescommand. npxresolves the mutable package version, and the installer retrieves mutable repository content.- The modified content is executed during installation or installed globally under the user's Agent Skill directory.
- The malicious Skill subsequently executes with the privileges of the user running the agent.
Impact Assessment
Successful exploitation could install or execute arbitrary code with the current user's privileges. The affected scope includes files, credentials, agent configuration, and other resources accessible to that user. The command does not itself request administrative privileges, so the dir ...[truncated 64 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the npm package to a reviewed version, for example by using an explicit
package@versionreference. - Pin the Skill repository to an immutable commit hash or signed release rather than a mutable branch.
- Publish a SHA-256 checksum or cryptographic signature for the distributable archive and require verification before installation.
- Remove
--yesfrom the recommended command when practical so users can review installation details. - Document the expected package version, repository commit, archive digest, and installed file manifest.
- Prefer installation from a locally downloaded and verified release artifact.
- Pin the npm package to a reviewed version, for example by using an explicit
