T08 · Insecure Dependencies
- Location
README.md:272- Finding
Unpinned Third-Party Package Execution via npx
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 272-279
Vulnerability Type: Unpinned third-party dependency execution
Risk Level: MediumVulnerable Code
bash # Install this skill only npx skills add flagos-ai/skills --skill skill-creator-flagos -a claude-code # Or install all Flagos skills at once npx skills add flagos-ai/skills -a claude-codeThe same instructions also appear in
README_zh.md, lines 270-277.Technical Analysis
The installation instructions invoke the
skillsnpm package throughnpxwithout specifying a package version, integrity hash, or trusted immutable source. If the package is not already installed locally,npxmay retrieve and execute the version currently resolved by the configured npm registry.Consequently, the code executed at installation time is not fixed to the version reviewed in this audit. A compromised package release, maintainer account, registry response, or upstream component could cause these commands to execute code that differs from the audited project. The subsequent installation of
flagos-ai/skillsalso relies on mutable upstream content without a documented commit pin or checksum.No evidence indicates that the currently bundled project is malicious. This finding concerns the mutable, unverified supply-chain execution path presented to users.
Attack Path
- An attacker compromises the npm package, a package maintainer account, the distribution channel, or another relevant upstream source.
- The attacker publishes or serves a modified version containing malicious installation or runtime behavior.
- A user follows the documented Quick Install procedure.
npxresolves, downloads, and executes the unpinned package under the user's account.- The malicious package accesses any files, environment variables, credentials, or network resources available to that user.
Impact Assessment
Successful exploitation cou ...[truncated 403 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the npm package to a reviewed, exact version rather than resolving the latest available release:
bash npx skills@<reviewed-exact-version> add flagos-ai/skills --skill skill-creator-flagos -a claude-code - Verify the selected release's provenance, integrity metadata, maintainer ownership, and published contents before recommending it.
- Prefer explicit installation through a lockfile followed by
npx --no-install, preventing an implicit network download during invocation. - Pin upstream repository content to a reviewed commit or signed release instead of a mutable branch.
- Publish checksums or signatures and document a verification procedure before installation.
- Present the existing manual copy procedure as the preferred installation method when immutable provenance cannot be guaranteed.
- Apply equivalent corrections to
README_zh.md, lines 270-277. - Advise users not to run installation commands with elevated privileges.
- Pin the npm package to a reviewed, exact version rather than resolving the latest available release:
