NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

checkout-mobile-input-emailnpm

Advisory published Updated

checkout-mobile-input-email is a confirmed malicious npm package (MAL-2026-12576) that executes malicious code on install (malicious version 35.6.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in checkout-mobile-input-email (npm)

MAL-2026-12576
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall checkout-mobile-input-email

What this malware does

On require('checkout-mobile-input-email'), index.js loads helpers.js which assembles hostnames via string-array.join("") (e.g. ["oob-worker.cf103-070.workers.","dev"].join(""), ["oob-","worker.cf102-baf.workers.d","ev"].join(""), and ['sdk.dl.wel1.','ru'].join("")) to reach oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, and DNS-TXT fallback resolvers under *.dl.wel1.ru. A platform-specific binary is downloaded, written to /tmp or %TEMP% under disguised names (.cache<hex>,.analytics_state, dotnet_diag_<hex>.exe), chmod'd 0755, and spawned detached via spawn("/bin/sh",...) with fp+' &' or via cmd.exe /c start /b at _helpers.js line 121-139. Destination hostnames are anonymous Cloudflare Workers subdomains unrelated to any legitimate 'checkout mobile input email' functionality; the base64/DNS-TXT fallback resolver path constitutes a secondary exfil/download channel. A large sibling bundle lib/telemetry.js (~81 KB) ships in the tarball but is not require()'d from the traced modules; the executed native binary may reference or replace it.

Malicious versions

1 flagged
35.6.8

Indicators of compromise (SHA-256)

f9c13bf58568e58ecec010552f23cd8eb27cef188f4ed0c905e832fa0f8d0372

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for checkout-mobile-input-email (version 35.6.8).

  2. If you installed it — respond

    Remove checkout-mobile-input-email 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-input-email 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

No. checkout-mobile-input-email on npm has been identified as a malicious package (version 35.6.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015199

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks checkout-mobile-input-email-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
checkout-mobile-input-email (npm) malicious package — MAL-2026-12576 | O3 Security