Which versions of bnpl-blocks-atom-bnpl-dolyame-button are malicious?

The following npm versions of bnpl-blocks-atom-bnpl-dolyame-button are flagged malicious: 35.1.8. Treat any of these as compromised.

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

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

If bnpl-blocks-atom-bnpl-dolyame-button 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 bnpl-blocks-atom-bnpl-dolyame-button part of a known attack campaign?

Yes — bnpl-blocks-atom-bnpl-dolyame-button is associated with the IN-MAL-2026-015513 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-dolyame-button 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 bnpl-blocks-atom-bnpl-dolyame-button (version 35.1.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-atom-bnpl-dolyame-button across your stack and pipelines.

Malicious package

bnpl-blocks-atom-bnpl-dolyame-buttonnpm

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

Malicious code in bnpl-blocks-atom-bnpl-dolyame-button (npm)

MAL-2026-12871

Immediate action

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

npm uninstall bnpl-blocks-atom-bnpl-dolyame-button

What this malware does

On require, index.js loads setup.js which selects a platform-specific binary path for linux/darwin/win32, downloads it over HTTPS from hardcoded Cloudflare Workers hostnames (oob-worker.cf103-07.0.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT chunked fallback via sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, writes the payload to a disguised temp path, chmods it 0755, and spawns it detached via /bin/sh -c or cmd /c start. Destination hostnames and sensitive API names (child_process, chmodSync) are reconstructed at runtime from arrays of string fragments to defeat string scanners. Opt-out environment variables (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) and a benign 'analytics_state' filename are used as cover. There is no pinning, no signature check, and the destinations are unrelated to the package publisher. Installing or requiring the package causes an attacker-controlled binary to run on the host.

Malicious versions

1 flagged

35.1.8

Indicators of compromise (SHA-256)

953d88d16a72d63369a076b864facc257f63385eb38d220ca649b8712ff50277

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 bnpl-blocks-atom-bnpl-dolyame-button (version 35.1.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-atom-bnpl-dolyame-button across your stack and pipelines.
If you installed it — respond
bnpl-blocks-atom-bnpl-dolyame-button 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-dolyame-button 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 bnpl-blocks-atom-bnpl-dolyame-button 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. bnpl-blocks-atom-bnpl-dolyame-button on npm has been identified as a malicious package (version 35.1.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015513

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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