T08 · Insecure Dependencies
- Location
SKILL.md:13- Finding
Unpinned fleets Package Is Automatically Downloaded and Executed
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 13
Vulnerability Type: Unpinned third-party package execution
Risk Level: HighVulnerable Code
bash npx -y fleets login --browser # device flow: opens URL + 8-char codeTechnical Analysis
The setup instructions invoke
npxwith the-yoption and do not specify a reviewed package version or integrity constraint. Consequently, npm resolves, downloads, and executes whicheverfleetsrelease the configured registry currently serves. The-yoption suppresses the interactive installation confirmation.This creates a supply-chain trust boundary that is not represented by a lockfile, version pin, checksum, or vendored implementation in the audited project. If the package, publisher account, registry response, or resolution environment is compromised, package lifecycle scripts or runtime code can execute with the privileges of the user running the command.
The audit found no evidence that the current
fleetspackage is malicious. The confirmed weakness is the automatic execution of mutable, unpinned third-party code.Attack Path
- An attacker compromises the npm package, its publisher account, or an applicable package-resolution path.
- The attacker publishes or serves a malicious release under the
fleetspackage name. - A user follows the documented setup command.
npx -yresolves the current package release without requesting confirmation.- Malicious lifecycle or runtime code executes in the user's environment.
- The code may read accessible files and environment variables, including
FLEETS_TOKEN, or initiate network connections using the user's privileges.
Impact Assessment
Successful exploitation could provide arbitrary code execution under the account that launches the command. The resulting scope includes that account's readable files, environment variables, network access, and writable resources. Analy ...[truncated 227 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the CLI to a reviewed, immutable version, for example:
bash npx --yes fleets@X.Y.Z login --browser - Regularly review and deliberately update the pinned version rather than implicitly accepting the latest release.
- Where supported, use a lockfile and npm integrity metadata to verify the downloaded artifact.
- Document the expected npm publisher, source repository, and package identity so users can verify provenance.
- Prefer installing dependencies in a constrained environment with minimal filesystem access and no unrelated secrets.
- Avoid exposing
FLEETS_TOKENor other sensitive environment variables while executing newly downloaded package code. - Consider removing
-ywhen automatic, unattended package installation is unnecessary.
- Pin the CLI to a reviewed, immutable version, for example:
