checkout-parameters
Checkout parameters abstraction layer
This report shows the evidence for checkout-parameters@35.8.5, the only known version.
This package appears in our research on the August 2026 dependency confusion campaign, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe package's advertised checkout-parameter API does not require a silent native downloader. Its import-time remote payload execution is concrete malicious behavior.
Decision evidence
public snapshot- index.js imports _vendor on every package import.
- _vendor.js downloads platform binaries from hard-coded hosts or DNS TXT.
- _vendor.js writes payloads to temp storage, chmods them, then detached-spawns them.
- No hash/signature verification is implemented despite the integrity comment.
- lib/telemetry.js contains a configurable duplicate downloader/executor.
- package.json has no lifecycle scripts.
- _vendor.js honors telemetry opt-out variables.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
_vendor.jsView on unpkg · L2A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_vendor.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to checkout-parameters@35.8.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing checkout-parameters@35.8.5. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.