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

bnpl-blocks-atom-bnpl-dropdownnpm

Advisory published Updated

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

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

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

What this malware does

index.js unconditionally requires./support at package load. support.js reconstructs a list of Cloudflare Workers hostnames (oob-worker.cf103-070.workers.de, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev) and DNS discovery domains (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru) from split string literals joined at runtime, fetches an opaque binary via https.get, writes it to /tmp under cover-story names such as.cache<rand> and dotnet_diag<rand>.exe, chmods it 0755, and spawns it detached via /bin/sh -c or cmd. Platform-branched dispatch covers Linux, macOS, and Windows. A sibling lib/telemetry.js also concatenates the module name 'child_process' to evade static scanners. Environment-variable opt-outs (DISABLE_TELEMETRY, DO_NOT_TRACK) and a /tmp/.analytics_state freshness marker serve as cover for the dropper. Requiring or installing the package results in full-host code execution from unpinned, unverified, obfuscated attacker-controlled infrastructure.

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.5.5

Indicators of compromise (SHA-256)

fe2cdda88c39101955d7333e81f68b9cefe2dbfab23862351194168e2c61e5e9
b42d82e07577f5c12abd78af481dff80c471c910111551b755368719ab753396

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for bnpl-blocks-atom-bnpl-dropdown (version 35.5.5).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015514GHSA-78qc-hpf4-c2hh

References

Credits

  • Amazon Inspector · finder

Detect & block this

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