T08 · Insecure Dependencies
- Location
SKILL.md:31- Finding
Execution of Unpinned Third-Party npm Package
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:31-32,SKILL.md:41-46,SKILL.md:63-66
Vulnerability Type: Unpinned and unaudited third-party package execution
Risk Level: MediumVulnerable Code Snippets
bash npx our-autoskillsbash npx our-autoskills npx our-autoskills detect npx our-autoskills install npx our-autoskills list npx our-autoskills doctorbash npm install -g our-autoskills npx our-autoskillsTechnical Analysis
The documentation instructs users to execute
our-autoskillsdirectly from the npm registry without pinning an exact version or verifying an integrity digest. Depending on the local npm configuration and cache state,npx our-autoskillscan retrieve the current registry release and immediately execute its CLI code.The project contains only
SKILL.md; it does not include the package implementation, a lockfile, dependency metadata, or integrity information that would allow the executed code and its transitive dependencies to be reviewed as part of this audit. The documented global installation also creates a longer-lived installation in the user's npm environment.The package is described as installing additional Agent Skills. Consequently, compromise of the npm package, its maintainer account, or one of its transitive dependencies could introduce additional unreviewed components and expand the supply-chain exposure.
No evidence establishes that the current npm package is malicious. The risk arises from executing mutable, externally hosted code without version pinning or integrity verification.
Attack Path
- An attacker compromises the npm package, a maintainer account, or a transitive dependency, or publishes a malicious future release.
- A user follows the instructions in
SKILL.mdand runsnpx our-autoskillsor installs the package globally. - npm resolves the mutable package release from the registry.
- Package li ...[truncated 905 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the package to an exact reviewed version rather than resolving the latest release:
bash npx --yes our-autoskills@<reviewed-exact-version> - Record and verify the package tarball integrity digest before execution.
- Include the auditable implementation in the project or reference a reproducible, immutable source revision.
- Add a lockfile and review all direct and transitive dependencies.
- Avoid global installation unless it is strictly necessary; prefer an isolated, least-privileged environment.
- Disable npm lifecycle scripts during installation where functionality permits, and separately review any scripts that must run.
- Require explicit user confirmation before installing each additional Skill.
- Pin every installed Skill to an immutable reviewed version and verify its provenance and integrity.
- Run installation and detection operations without elevated privileges and with minimal access to secrets and sensitive directories.
- Pin the package to an exact reviewed version rather than resolving the latest release:
