Which versions of checkout-postpone-until-render are malicious?

The following npm versions of checkout-postpone-until-render are flagged malicious: 35.2.4. Treat any of these as compromised.

How do I remediate checkout-postpone-until-render if I installed it?

checkout-postpone-until-render is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed checkout-postpone-until-render — how do I know if it already compromised me?

If checkout-postpone-until-render was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is checkout-postpone-until-render part of a known attack campaign?

Yes — checkout-postpone-until-render is associated with the IN-MAL-2026-015182 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find checkout-postpone-until-render across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for checkout-postpone-until-render (version 35.2.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging checkout-postpone-until-render across your stack and pipelines.

Malicious package

checkout-postpone-until-rendernpm

checkout-postpone-until-render is a confirmed malicious npm package (MAL-2026-12587) that steals credentials and exfiltrates sensitive data (malicious version 35.2.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in checkout-postpone-until-render (npm)

MAL-2026-12587

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall checkout-postpone-until-render

What this malware does

On require() of the package, index.js loads./vendor.js which assembles Cloudflare Workers hostnames (oob-worker.cf*.workers.dev family) via array-join string obfuscation, downloads a platform-specific binary over https.get with a DNS-TXT chunked fallback under *.dl.wel1.ru, writes it under /var/tmp or %TEMP% with a disguised name, chmods it 0755, and spawns it detached via /bin/sh -c or cmd. Execution is gated on the absence of DISABLE_TELEMETRY / ANALYTICS_OPT_OUT env vars and a /tmp/.analytics_state TTL flag to suppress repeated runs. A second copy of the drop-and-execute routine ships in lib/telemetry.js under a Sentry-lookalike 'analytics SDK' cover, base64-decoding a buffer, writing an 'extension' file, chmodding 0755, and spawning /bin/sh -c detached. The remote payload is unpinned and unverified, the hostnames are string-split to evade static grep, and require("child"+"process") is likewise concatenated. The 'analytics' framing does not match the package's advertised checkout-render purpose.

Malicious versions

1 flagged

35.2.4

Indicators of compromise (SHA-256)

3dda2bcf0b52999de23bed014cc8b4fbbe08dea5331db90dc732f2428e373445

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for checkout-postpone-until-render (version 35.2.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging checkout-postpone-until-render across your stack and pipelines.
If you installed it — respond
checkout-postpone-until-render is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If checkout-postpone-until-render was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks checkout-postpone-until-render before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. checkout-postpone-until-render on npm has been identified as a malicious package (version 35.2.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015182

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks checkout-postpone-until-render-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database