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

bnpl-blocks-atom-bnpl-fade-overflownpm

Advisory published Updated

bnpl-blocks-atom-bnpl-fade-overflow is a confirmed malicious npm package (MAL-2026-12874) that executes malicious code on install (malicious version 35.7.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bnpl-blocks-atom-bnpl-fade-overflow (npm)

MAL-2026-12874
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bnpl-blocks-atom-bnpl-fade-overflow

What this malware does

On require() of this package, index.js loads runtime.js which selects a platform-specific payload path, fetches bytes over HTTPS from string-split-obfuscated *.workers.dev mirrors (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT chunked-base64 fallback via sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, writes the bytes to /var/tmp/.cache<rand> or %TEMP%\dotnet_diag_<rand>.exe, chmods 0755, and spawns the file detached via /bin/sh -c or cmd.exe /c start. Hostnames are reconstructed at runtime from fragmented string literals joined with.join("") to evade static matching. lib/telemetry.js ships an equivalent fetch/write/chmod-755/spawn chain disguised as an analytics SDK; it is bundled in the tarball though not reached from the current entrypoint. The staged filenames (dotnet_diag_.exe,.cache_) are cover-story names for opaque native payloads executed on the installer's host.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
35.7.2

Indicators of compromise (SHA-256)

f78c9360e199f852a5b395b6549e12b6334ec3dce096462a4404a3a0e809f545
69f76ef9cc60214327c95cd87319672e0f624c8d2cb60f50081ac9776f43ea71

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for bnpl-blocks-atom-bnpl-fade-overflow (version 35.7.2).

  2. If you installed it — respond

    Remove bnpl-blocks-atom-bnpl-fade-overflow 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 bnpl-blocks-atom-bnpl-fade-overflow 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-fade-overflow on npm has been identified as a malicious package (version 35.7.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015509GHSA-cmmv-wrqx-q5f8

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-atom-bnpl-fade-overflow-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
bnpl-blocks-atom-bnpl-fade-overflow (npm) malicious package — MAL-2026-12874 | O3 Security