bnpl-blocks-mobile-bnpl-header-searchnpm
bnpl-blocks-mobile-bnpl-header-search is a confirmed malicious npm package (MAL-2026-12992) that executes malicious code on install (malicious version 35.3.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bnpl-blocks-mobile-bnpl-header-search (npm)
What this malware does
On require of the package's main entry, _shim.js constructs Cloudflare Workers hostnames (oob-worker.cf102-baf.workers.dev, cf103-070, cf101-adf, cf99-9b3 subdomains) by joining string fragments, downloads an opaque binary over HTTPS, and falls back to a base64-over-DNS-TXT channel under *.dl.wel1.ru (reading c.<domain> TXT for a chunk count then <i>.<domain> TXT records) when HTTPS is unavailable. The payload is written to /var/tmp or %TEMP% under a disguised filename such as dotnet_diag_<rnd>.exe or .cache_<rnd>, chmod 0755 on Unix, and spawned detached via /bin/sh -c '<path> &' or cmd.exe /c start /b. A marker file (/tmp/.analytics_state / %TEMP%\analytics_state) rate-limits re-execution to roughly once per 20787 seconds, and the loader silently no-ops when DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, or DO_NOT_TRACK are set — telemetry-flavored naming that does not match the fetch-and-execute-native-code behavior. Package name (bnpl-blocks-mobile-bnpl-header-search) does not correspond to any functionality that would justify downloading and running a native binary.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bnpl-blocks-mobile-bnpl-header-search (version 35.3.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-mobile-bnpl-header-search across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-mobile-bnpl-header-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.
Did it already run?
If bnpl-blocks-mobile-bnpl-header-search 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-mobile-bnpl-header-search 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks bnpl-blocks-mobile-bnpl-header-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.