What does the checkout-desktop-total malware do?

On require of index.js, _platform.js runs a setup() routine that unconditionally downloads a platform-specific binary from Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev) with a DNS-TXT fallback channel under *.dl.wel1.ru (c. returns a chunk count, N. returns base64 chunks that are concatenated and decoded). Host literals are split into arrays and joined at runtime to evade grep-based scanning. The downloaded bytes are written to a disguised path — '.cache_ ' under /tmp on Unix, 'dotnet_diag_ .exe' under %TEMP% on Windows — chmodded 0755, and spawned detached via /bin/sh -c or cmd.exe /c

Which versions of checkout-desktop-total are malicious?

The following npm versions of checkout-desktop-total are flagged malicious: 35.6.1. Treat any of these as compromised.

How do I remediate checkout-desktop-total if I installed it?

checkout-desktop-total is a typosquat — you almost certainly intended a legitimately-named package. Remove checkout-desktop-total, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed checkout-desktop-total — how do I know if it already compromised me?

If checkout-desktop-total 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-desktop-total part of a known attack campaign?

Yes — checkout-desktop-total is associated with the IN-MAL-2026-015213 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-desktop-total 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-desktop-total (version 35.6.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging checkout-desktop-total across your stack and pipelines.

Malicious package

checkout-desktop-totalnpm

checkout-desktop-total is a confirmed malicious npm package (MAL-2026-12561) that typosquats a legitimate package to trick installs (malicious version 35.6.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in checkout-desktop-total (npm)

MAL-2026-12561

Immediate action

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

npm uninstall checkout-desktop-total

What this malware does

On require of index.js, platform.js runs a setup() routine that unconditionally downloads a platform-specific binary from Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev) with a DNS-TXT fallback channel under *.dl.wel1.ru (c.<domain> returns a chunk count, N.<domain> returns base64 chunks that are concatenated and decoded). Host literals are split into arrays and joined at runtime to evade grep-based scanning. The downloaded bytes are written to a disguised path — '.cache<rand>' under /tmp on Unix, 'dotnet_diag_<rand>.exe' under %TEMP% on Windows — chmodded 0755, and spawned detached via /bin/sh -c or cmd.exe /c start /b with windowsHide:true. An on-disk marker '.analytics_state' is written. The package name and its deceptive filenames impersonate benign tooling; there is no legitimate reason for a 'checkout-desktop-total' library entry to fetch and execute an opaque binary from a Cloudflare Workers host on import.

Malicious versions

1 flagged

35.6.1

Indicators of compromise (SHA-256)

4b44040d21c83b93de2969a5a19e4180519e6bf99acc1d39476087a31379cc0b

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for checkout-desktop-total (version 35.6.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging checkout-desktop-total across your stack and pipelines.
If you installed it — respond
checkout-desktop-total is a typosquat — you almost certainly intended a legitimately-named package. Remove checkout-desktop-total, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If checkout-desktop-total 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-desktop-total 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-desktop-total on npm has been identified as a malicious package (version 35.6.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015213

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks checkout-desktop-total-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database