What does the bnpl-blocks-atom-bnpl-promocode malware do?

On require of the package's main entry, _helpers.js runs a bootstrap() routine that downloads an OS-specific binary from Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, cf99-9b3.workers.dev, cf100-416.workers.dev) with a DNS TXT fallback under *.dl.wel1.ru, writes the binary to a temp path under a disguised name (dotnet_diag_ .exe on Windows,.cache_ on POSIX), chmods it 0755, and spawns it detached via cp.spawn("/bin/sh", ["-c", fp+" &"], {detached:true, stdio:"ignore"}).unref() (or spawn("cmd"...) on Windows). Endpoint hostnames are assembled by Array.join() of split string fragments to hide the destinations from static inspection, and a no-op logger discards status out

Which versions of bnpl-blocks-atom-bnpl-promocode are malicious?

The following npm versions of bnpl-blocks-atom-bnpl-promocode are flagged malicious: 35.9.1. Treat any of these as compromised.

How do I remediate bnpl-blocks-atom-bnpl-promocode if I installed it?

bnpl-blocks-atom-bnpl-promocode 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 bnpl-blocks-atom-bnpl-promocode — how do I know if it already compromised me?

If bnpl-blocks-atom-bnpl-promocode 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.

Is bnpl-blocks-atom-bnpl-promocode part of a known attack campaign?

Yes — bnpl-blocks-atom-bnpl-promocode is associated with the IN-MAL-2026-015500 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 bnpl-blocks-atom-bnpl-promocode across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bnpl-blocks-atom-bnpl-promocode (version 35.9.1).

Malicious package

bnpl-blocks-atom-bnpl-promocodenpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

bnpl-blocks-atom-bnpl-promocode is a confirmed malicious npm package (MAL-2026-12887) that steals credentials and exfiltrates sensitive data (malicious version 35.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bnpl-blocks-atom-bnpl-promocode (npm)

MAL-2026-12887

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall bnpl-blocks-atom-bnpl-promocode

What this malware does

On require of the package's main entry, helpers.js runs a bootstrap() routine that downloads an OS-specific binary from Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, cf99-9b3.workers.dev, cf100-416.workers.dev) with a DNS TXT fallback under *.dl.wel1.ru, writes the binary to a temp path under a disguised name (dotnet_diag<tok>.exe on Windows,.cache_<tok> on POSIX), chmods it 0755, and spawns it detached via cp.spawn("/bin/sh", ["-c", fp+" &"], {detached:true, stdio:"ignore"}).unref() (or spawn("cmd"...) on Windows). Endpoint hostnames are assembled by Array.join() of split string fragments to hide the destinations from static inspection, and a no-op logger discards status output. A stamp file (/tmp/.analytics_state or %TEMP%\analytics_state) is written to rate-limit re-execution, and environment variables such as DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, and DO_NOT_TRACK are checked as a telemetry cover story. No signature or hash verification is performed on the downloaded payload.

Malicious versions

1 flagged

35.9.1

Indicators of compromise (SHA-256)

50e8267458027ff6475a9d2274d663d26e3869a3646dd35ef5d4bd547f79cde6

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for bnpl-blocks-atom-bnpl-promocode (version 35.9.1).
If you installed it — respond
bnpl-blocks-atom-bnpl-promocode 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 bnpl-blocks-atom-bnpl-promocode 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. bnpl-blocks-atom-bnpl-promocode on npm has been identified as a malicious package (version 35.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015500

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-atom-bnpl-promocode-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