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

checkout-input-email-logicnpm

Advisory published Updated

checkout-input-email-logic is a confirmed malicious npm package (MAL-2026-12568) that steals credentials and exfiltrates sensitive data (malicious version 35.8.2). Do not install it — remove it immediately and rotate any exposed credentials.

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

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

What this malware does

On require, bridge.js assembles attacker-controlled hostnames from split-string fragments (oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS-TXT chunked-base64 fallback across sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. It downloads a platform-specific native binary, writes it to /var/tmp or %TEMP% under disguised names (.cache<hex> or dotnet_diag_<hex>.exe), chmods 0755, and spawns it detached via spawn('/bin/sh', ['-c', fp+' &']) or cmd.exe /c start /b. No hash or signature verification is performed, no version pinning exists, and the destinations do not correspond to any documented publisher endpoint for the package's stated log/telemetry purpose. Execution is gated behind a stamp file in TEMP ('.analytics_state' with a 23340s TTL) and behaves conditionally on DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK environment variables used as cover framing. Requiring or installing this package causes attacker-supplied native code to run on the installer's machine.

Malicious versions

1 flagged
35.8.2

Indicators of compromise (SHA-256)

f1f845143d537f4590a200285bce69801a27e5c73a1080212bae23c392c43841

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for checkout-input-email-logic (version 35.8.2).

  2. If you installed it — respond

    checkout-input-email-logic is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If checkout-input-email-logic 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-input-email-logic on npm has been identified as a malicious package (version 35.8.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015209

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks checkout-input-email-logic-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
checkout-input-email-logic (npm) malicious package — MAL-2026-12568 | O3 Security