Which versions of checkout-mobile-bnpl are malicious?

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

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

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

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

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

Malicious package

checkout-mobile-bnplnpm

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

Malicious code in checkout-mobile-bnpl (npm)

MAL-2026-12572

Immediate action

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

npm uninstall checkout-mobile-bnpl

What this malware does

index.js requires./helpers on load. helpers.js reconstructs three Cloudflare Workers hostnames (oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev) from split-string fragments, plus a DNS-TXT fallback channel under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru that reassembles base64 chunks retrieved via resolveTxt. It downloads a platform-specific binary (linux_x64, linux_arm64, darwin, win32), writes it to /var/tmp or %TEMP% under a disguised name (.cache<hex> or dotnet_diag<hex>.exe), chmods 0755, and spawns it detached via /bin/sh -c or cmd /c start, with an mtime stamp to gate repeat execution. lib/telemetry.js (~81KB) carries a duplicate copy of the same dropper primitives (base64 chunking, DNS-based service discovery, spawn('/bin/sh',['-c',filePath+' &']), chmodSync 0755) framed as an analytics SDK; it is not reached from main in this version but is present as a staged alternate payload host. Package name impersonates checkout/BNPL tooling and the destinations are unrelated to any such service.

Malicious versions

1 flagged

35.6.9

Indicators of compromise (SHA-256)

0734507ccd6f61cb81c277d9e9215c90f0b8cff1bd16f0c3eacd399750d26b4f

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-mobile-bnpl (version 35.6.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging checkout-mobile-bnpl across your stack and pipelines.
If you installed it — respond
checkout-mobile-bnpl is a typosquat — you almost certainly intended a legitimately-named package. Remove checkout-mobile-bnpl, 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-bnpl 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-mobile-bnpl 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-mobile-bnpl on npm has been identified as a malicious package (version 35.6.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015198

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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