Which versions of bnpl-blocks-fonts are malicious?

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

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

Remove bnpl-blocks-fonts 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.

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

If bnpl-blocks-fonts 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-fonts part of a known attack campaign?

Yes — bnpl-blocks-fonts is associated with the IN-MAL-2026-015425 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-fonts 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-fonts (version 35.2.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-fonts across your stack and pipelines.

Malicious package

bnpl-blocks-fontsnpm

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

Malicious code in bnpl-blocks-fonts (npm)

MAL-2026-12948

Immediate action

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

npm uninstall bnpl-blocks-fonts

What this malware does

The package presents itself as a fonts helper but its index.js unconditionally requires./ext, which on module load fetches a platform-specific binary from hardcoded Cloudflare Workers subdomains (oob-worker.cf101-adf.workers.dev, cf99-9b3.workers.dev, cf100-416.workers.dev) with a DNS-TXT fallback channel over *.dl.wel1.ru (chunked base64 delivered via resolveTxt on c.<domain> and N.<domain>). Hostnames are split into array fragments and joined at runtime to evade static analysis. The fetched bytes are written to a disguised temp path (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmodded to 0755, and spawned detached via cp.spawn('/bin/sh', ['-c', fp+' &']) or cp.spawn('cmd',...). No hash or signature is verified and the payload is opaque. A parallel dropper in lib/telemetry.js mirrors the same design (base64 chunk decode, chmodSync via property-name splitting, shell spawn) as an alternate loader. The declared 'fonts' / 'analytics/telemetry' purpose does not match fetching and executing anonymous remote binaries at require time.

Malicious versions

1 flagged

35.2.2

Indicators of compromise (SHA-256)

5181e44b181b008c8345153784c66020faa73f1f591fc070a1f20f105ba8f2c6

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bnpl-blocks-fonts (version 35.2.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-fonts across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-fonts 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-fonts 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-fonts 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-fonts on npm has been identified as a malicious package (version 35.2.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015425

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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