Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

checkout-mobile-pay-buttonnpm

checkout-mobile-pay-button is a confirmed malicious npm package (MAL-2026-12352) that executes malicious code on install (malicious version 20.8.3). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2026-12352
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall checkout-mobile-pay-button

What this malware does

[email protected] is a lure package: its name and README describe a 'mobile pay button platform adapter', but index.js unconditionally require()'s loader.js on load. loader.js reconstructs attacker-controlled hostnames at runtime via string-split/join obfuscation (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev), downloads a platform-specific binary via https.get, writes it to /tmp or %TEMP% under a disguised name (.cache<hex> on Unix, dotnet_diag<hex>.exe on Windows), chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe with.unref(). A DNS TXT covert channel over tin.dl.well1.site / tina.dl.well1.site / ldr.dl.well1.site / win.dl.well1.site (c.<domain> chunk-count then i.<domain> base64 chunks) provides a fallback delivery path when the workers.dev origins fail. The exported CheckoutMobilePayButton class is a stub with no real functionality; the package's only effect on install/require is fetching and executing opaque attacker-controlled bytes on the installer's host.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
20.8.3

Indicators of compromise (SHA-256)

3299d3b20175ec3cd68c2355ccafd1e969237d93b2e708c92a9913ff323b19be
0ce331757d94d948eb0d5685493abeb7926a32a4884e1166787bcd51bd655866

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove checkout-mobile-pay-button from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If checkout-mobile-pay-button 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.

  4. How O3 protects you

    O3 blocks checkout-mobile-pay-button 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-pay-button on npm has been identified as a malicious package (version 20.8.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014733GHSA-c2h8-p68f-vf8m

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

checkout-mobile-pay-button (npm) malicious package — MAL-2026-12352 | O3 Security