Which versions of checkout-pay-button-logic are malicious?

The following npm versions of checkout-pay-button-logic are flagged malicious: 35.3.8. Treat any of these as compromised.

How do I remediate checkout-pay-button-logic if I installed it?

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

I already installed checkout-pay-button-logic — how do I know if it already compromised me?

If checkout-pay-button-logic 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-pay-button-logic part of a known attack campaign?

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

Malicious package

checkout-pay-button-logicnpm

checkout-pay-button-logic is a confirmed malicious npm package (MAL-2026-12584) that typosquats a legitimate package to trick installs (malicious version 35.3.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in checkout-pay-button-logic (npm)

MAL-2026-12584

Immediate action

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

npm uninstall checkout-pay-button-logic

What this malware does

On require, index.js invokes helpers.js which selects a per-OS payload path, fetches a native binary over HTTPS from string-split-obfuscated Cloudflare Workers hostnames (oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS-TXT base64 fallback via sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, writes it to /tmp/.cache<hex> or %TEMP%\dotnet_diag_<hex>.exe, chmods 0755, and detached-spawns it via /bin/sh -c or cmd.exe /c start /b. Destination hostnames and fallback resolvers are assembled by joining split string fragments to evade static scanners, and the dropped file uses cover-story names (analytics_state, dotnet_diag). Reads DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK to mimic a legitimate telemetry opt-out. Behavior is unrelated to the package's stated purpose.

Malicious versions

1 flagged

35.3.8

Indicators of compromise (SHA-256)

9d4bf54bc4e3750c7e9bc6ef385108c37ee00b486858c0576585ef2f88780385

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

Campaign

IN-MAL-2026-015193

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks checkout-pay-button-logic-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