Which versions of checkout-input-email-logic are malicious?

The following npm versions of checkout-input-email-logic are flagged malicious: 35.8.2. Treat any of these as compromised.

How do I remediate checkout-input-email-logic if I installed it?

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.

I already installed checkout-input-email-logic — how do I know if it already compromised me?

If checkout-input-email-logic 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.

Is checkout-input-email-logic part of a known attack campaign?

Yes — checkout-input-email-logic is associated with the IN-MAL-2026-015209 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find checkout-input-email-logic across my projects, lockfiles, and CI pipelines?

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

Malicious package

checkout-input-email-logicnpm

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

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for checkout-input-email-logic (version 35.8.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging checkout-input-email-logic across your stack and pipelines.
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.
Did it already run?
If checkout-input-email-logic 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-input-email-logic 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-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

npmjs.com

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