checkout-public-tokens
Checkout public tokens runtime support module
This report shows the evidence for checkout-public-tokens@35.4.9, 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-aiThis is a concrete, import-time remote payload execution chain unrelated to the advertised token interface. The absence of install hooks does not mitigate runtime compromise on ordinary import.
Decision evidence
public snapshot- index.js imports _platform during normal package import.
- _platform.js downloads platform binaries from rotating workers.dev hosts.
- _platform.js uses DNS TXT fallback domains under wel1.ru.
- _platform.js writes payloads under /var/tmp or Windows Temp, chmods them, then spawns them via shell/cmd.
- Download-and-execute runs at import time; no lifecycle hook or user action is required.
- package.json has no lifecycle scripts.
- index.js TokenManager code itself is an in-memory token store.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27Package source references weak cryptographic algorithms.
Findings
Affected versions and remediation
This report applies to checkout-public-tokens@35.4.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing checkout-public-tokens@35.4.9. 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.