Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

bnpl-blocks-seo-toolsnpm

bnpl-blocks-seo-tools is a confirmed malicious npm package (MAL-2026-13016) that typosquats a legitimate package to trick installs (malicious version 35.2.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bnpl-blocks-seo-tools (npm)

MAL-2026-13016
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bnpl-blocks-seo-tools

What this malware does

[email protected] declares itself an SEO tool but on module load (index.js requires./support.js) fetches a platform-specific native binary from one of several Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS-TXT-record fallback channel to sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru. The destination hostnames are reconstructed at runtime from split string arrays joined with.join("") to evade static string matching. The fetched binary is written to /tmp or %TEMP% under a disguised name (.cache<hex> on POSIX, dotnet_diag_<hex>.exe on Windows mimicking a.NET diagnostics tool), chmod 0755, and spawned detached with stdio ignored via spawn("/bin/sh") / spawn("cmd"). Execution is gated by a /tmp stamp file for once-per-6h cadence and suppressed when DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK are set, reducing detection footprint. The stated package purpose has no relationship to fetching and executing an unsigned native binary.

Malicious versions

1 flagged
35.2.3

Indicators of compromise (SHA-256)

fafe459f610c3c0c55f043148b4900bc1c70b4f02adfc7a440afbe115ca3b36a

Detection & response playbook

Typosquat

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bnpl-blocks-seo-tools (version 35.2.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-seo-tools across your stack and pipelines.

  2. If you installed it — respond

    bnpl-blocks-seo-tools is a typosquat — you almost certainly intended a legitimately-named package. Remove bnpl-blocks-seo-tools, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

    If bnpl-blocks-seo-tools 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.

  4. How O3 protects you

    O3 blocks bnpl-blocks-seo-tools 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

No. bnpl-blocks-seo-tools on npm has been identified as a malicious package (version 35.2.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015374

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-seo-tools-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-seo-tools (npm) malicious package — MAL-2026-13016 | O3 Security