T08 · Insecure Dependencies
- Location
README.md:20- Finding
Unpinned Third-Party Installer Execution Through npx
- Content
View full analysis
Vulnerability Details
File Location:
README.md:20
Vulnerability Type: Supply-chain risk from an unpinned executable dependency
Risk Level: MediumVulnerable Code
bash npx skills add lee-agi/agent-os-asset -g -yTechnical Analysis
The documented installation command invokes the third-party
skillspackage throughnpxwithout specifying an exact reviewed version or integrity value. When the package is unavailable locally,npxmay retrieve and execute its currently published version. The-yoption suppresses the normal confirmation prompt.Consequently, the code executed during installation is not limited to the version reviewed as part of this audit. A compromised registry account, package takeover, or malicious future package release could change the effective installer payload after this project has been reviewed.
This finding concerns the documented installation path rather than malicious code found in the repository itself.
Attack Path
- An attacker compromises the registry package, publisher account, or another component involved in resolving the unpinned
skillspackage. - The attacker publishes a malicious package version containing hostile CLI or lifecycle code.
- A user follows the installation command in
README.md. npxresolves and downloads the attacker-controlled current version.- Because no exact version or integrity constraint is present, and confirmation is suppressed by
-y, the downloaded code executes with the privileges of the invoking user.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the invoking user's privileges during installation. Depending on that user's permissions, malicious installer code could read accessible files and credentials, alter user-owned data, install persistence, or modify development tooling and configuration.
No evidence was found that the audited repository itself perfo ...[truncated 119 chars]
- An attacker compromises the registry package, publisher account, or another component involved in resolving the unpinned
- Remediation
View remediation
Remediation Suggestions
-
Pin the installer package to an exact, reviewed version, for example:
bash npx skills@<audited-exact-version> add lee-agi/agent-os-asset -g -
Remove
-yso users can inspect and approve unexpected package retrieval. -
Document the expected publisher, package version, and package-manager registry.
-
Publish and verify integrity hashes or signed release artifacts before execution.
-
Offer a non-executing installation alternative based on a versioned, checksummed archive.
-
In CI or managed environments, use a lockfile, trusted internal mirror, or preapproved installer binary rather than resolving the latest package dynamically.
-
