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

bnpl-blocks-independent-bnpl-searchnpm

Advisory published Updated

bnpl-blocks-independent-bnpl-search is a confirmed malicious npm package (MAL-2026-12341) that executes malicious code on install (malicious version 20.2.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bnpl-blocks-independent-bnpl-search (npm)

MAL-2026-12341
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bnpl-blocks-independent-bnpl-search

What this malware does

On require of the package, index.js loads _runtime.js which downloads a platform-specific binary from runtime-assembled *.workers.dev hosts (oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev), writes it under /tmp or %TEMP% with a disguised name, chmods 0755 on POSIX, and spawns it detached via /bin/sh -c or cmd /c start. Destination hostnames are assembled from split string fragments joined at runtime to evade static URL scanners. When HTTPS fetches fail, the loader falls back to base64-encoded chunks retrieved from DNS TXT records under attacker-controlled subdomains of dl.well1.site (tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site), reassembling and executing the payload from the encoded chunks. A second file lib/telemetry.js shipped in the tarball contains a matching download-decode-chmod-spawn class with the same operator shape.

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
20.2.9

Indicators of compromise (SHA-256)

e70389e1435e74337e9c402d824a2e90eeb0b2e9f82fc670035973a18382c558
a705b5542aaff7493fd599ff03512f0c2729bb2320e56828318ddfae37b012d3

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for bnpl-blocks-independent-bnpl-search (version 20.2.9).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-014702GHSA-v43r-98qv-2v96

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-independent-bnpl-search-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.

Explore

bnpl-blocks-independent-bnpl-search (npm) malicious package — MAL-2026-12341 | O3 Security