Which versions of bnpl-blocks-markdown are malicious?

The following npm versions of bnpl-blocks-markdown are flagged malicious: 35.4.1. Treat any of these as compromised.

How do I remediate bnpl-blocks-markdown if I installed it?

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

I already installed bnpl-blocks-markdown — how do I know if it already compromised me?

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

Is bnpl-blocks-markdown part of a known attack campaign?

Yes — bnpl-blocks-markdown is associated with the IN-MAL-2026-015407 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find bnpl-blocks-markdown across my projects, lockfiles, and CI pipelines?

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

Malicious package

bnpl-blocks-markdownnpm

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

Malicious code in bnpl-blocks-markdown (npm)

MAL-2026-12976

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall bnpl-blocks-markdown

What this malware does

On require('bnpl-blocks-markdown'), index.js loads bootstrap.js which downloads a platform-specific binary from runtime-assembled Cloudflare Workers hosts (strings such as ['oob-worker.cf100-416.workers','.d','ev'].join('') and ['sdk.dl.','wel','1.r','u'].join('')), with a base64-over-DNS-TXT fallback channel via wel1.ru subdomains. The fetched bytes are written to /tmp or %TEMP% under disguised filenames mimicking system tools (e.g..cache<hex>, dotnet_diag_<hex>.exe), chmod 0755'd, and spawned detached via /bin/sh -c or cmd. Env-var names DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK and filenames like analytics_state are cover-story framing; the package's advertised purpose is a markdown utility, which has no need to fetch and execute an arch-specific native binary from obfuscated hosts at import time. This is a classic import-time dropper with attacker-controlled code execution on the installer's host.

Malicious versions

1 flagged

35.4.1

Indicators of compromise (SHA-256)

161162281afaf68fd193e2521beaf60d32c850e29cc276192497eee09646a55a

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bnpl-blocks-markdown (version 35.4.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-markdown across your stack and pipelines.
If you installed it — respond
bnpl-blocks-markdown is a typosquat — you almost certainly intended a legitimately-named package. Remove bnpl-blocks-markdown, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If bnpl-blocks-markdown 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-markdown 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-markdown on npm has been identified as a malicious package (version 35.4.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015407

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-markdown-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