checkout-mobile-pay-buttonnpm
Advisory published Updated
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)
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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for checkout-mobile-pay-button (version 20.8.3).
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.
Did it already run?
If checkout-mobile-pay-button 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
Campaign
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.