checkout-postpone-until-render
Checkout postpone until render abstraction layer
This report shows the evidence for checkout-postpone-until-render@35.2.4, 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 advertised abstraction has no need for an import-time remote executable loader. The concrete network-to-disk-to-detached-process chain is malicious remote code execution.
Decision evidence
public snapshot- index.js imports _vendor.js on every package import.
- _vendor.js fetches platform-specific binaries from obfuscated hosts.
- _vendor.js falls back to DNS TXT payload delivery.
- Downloaded bytes are written, chmodded, and launched detached.
- Execution is automatic at import, not an explicit user command.
- package.json has no lifecycle scripts.
- No credential collection or exfiltration is evident in the entrypoint path.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
_vendor.jsView on unpkg · L4A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_vendor.jsView on unpkg · L4Findings
Affected versions and remediation
This report applies to checkout-postpone-until-render@35.2.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing checkout-postpone-until-render@35.2.4. 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.