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

bnpl-blocks-atom-bnpl-search-inputnpm

Advisory published Updated

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

Malicious code in bnpl-blocks-atom-bnpl-search-input (npm)

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

What this malware does

On require, bridge.js fetches a platform-specific binary from string-split-obfuscated Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev) and wel1.ru subdomains (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru), with a DNS-TXT reassembly fallback. The payload is written to /tmp or %TEMP% under disguised names (dotnet_diag<rand>.exe on Windows,.cache_<rand> on Unix), chmodded 0755, and spawned detached via cmd.exe or /bin/sh. Destinations are assembled from split string arrays to evade static analysis, and a marker-file cache plus DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK opt-out gates hide re-execution. The package advertises itself as an unrelated 'search input SDK', so the fetched binary has no relationship to the declared purpose. Loading the module in any consumer executes attacker-controlled native code 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.9.7

Indicators of compromise (SHA-256)

4f6cce4434c5b69e3ce6547672267cf91a8d243e9970fe13b9b669e7f7a7b91b
15be247a88e3e07c31cde3b64de7155c34a3860cce2d88978e3d823325960266

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for bnpl-blocks-atom-bnpl-search-input (version 35.9.7).

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-015487GHSA-pvq7-rm52-m5g7

References

Credits

  • Amazon Inspector · finder

Detect & block this

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