checkout-mobile-input-cardnpm
checkout-mobile-input-card is a confirmed malicious npm package (MAL-2026-12575) that typosquats a legitimate package to trick installs (malicious version 35.7.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in checkout-mobile-input-card (npm)
What this malware does
On require() of the package, index.js loads shim.js which downloads a platform-specific binary from obfuscated Cloudflare Workers subdomains (hostnames reconstructed via array-join splits such as ["oob-worker.cf103-070.wor","kers.","de","v"].join("")) with a DNS TXT covert-channel fallback that reassembles a base64-encoded binary from numbered TXT records under *.dl.wel1.ru. The downloaded payload is written to /var/tmp/.cache_XXXX on Unix or %TEMP%\dotnet_diag_XXXX.exe on Windows (masquerading as cache/diagnostic files), chmod 755'd, and spawned detached via /bin/sh -c or cmd.exe /c start /b. Additional string-splitting obfuscates identifiers such as require("child" + "process") and fs["chmod" + "Sync"]. The package name mimics a legitimate checkout/payments component.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for checkout-mobile-input-card (version 35.7.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging checkout-mobile-input-card across your stack and pipelines.
If you installed it — respond
checkout-mobile-input-card is a typosquat — you almost certainly intended a legitimately-named package. Remove checkout-mobile-input-card, 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-input-card 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-input-card 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks checkout-mobile-input-card-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.