Which versions of checkout-mobile-total are malicious?

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

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

checkout-mobile-total is a typosquat — you almost certainly intended a legitimately-named package. Remove checkout-mobile-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-mobile-total — how do I know if it already compromised me?

If checkout-mobile-total was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is checkout-mobile-total part of a known attack campaign?

Yes — checkout-mobile-total is associated with the IN-MAL-2026-015192 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-mobile-total across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for checkout-mobile-total (version 35.8.9).

Malicious package

checkout-mobile-totalnpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

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

Malicious code in checkout-mobile-total (npm)

MAL-2026-12580

Immediate action

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

npm uninstall checkout-mobile-total

What this malware does

On require of the package, index.js unconditionally loads vendor.js, which fetches a platform-specific binary from hardcoded Cloudflare Workers hosts (e.g. oob-worker.cf100-416.workers.dev) assembled by joining split string fragments, with a DNS-TXT covert-channel fallback to *.dl.wel1.ru. The retrieved payload is written to /var/tmp or %TEMP% under disguised names (.cache<rnd>, dotnet_diag_<rnd>.exe), chmodded 0755, and spawned detached via /bin/sh -c or cmd.exe. No hash or signature verification is performed, hostnames are unrelated to any declared publisher, and the destinations are concealed via string-split obfuscation. Package name mimics a checkout/payments library, consistent with typosquat lure targeting mobile checkout tooling.

Malicious versions

1 flagged

35.8.9

Indicators of compromise (SHA-256)

c1943ab64ce84576c6fef87d3b46187d0e442941f691d645adfe5f73595cfe9a

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for checkout-mobile-total (version 35.8.9).
If you installed it — respond
checkout-mobile-total is a typosquat — you almost certainly intended a legitimately-named package. Remove checkout-mobile-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-mobile-total was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-015192

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks checkout-mobile-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