Which versions of bnpl-blocks-desktop-bnpl-text-block are malicious?

The following npm versions of bnpl-blocks-desktop-bnpl-text-block are flagged malicious: 35.9.4. Treat any of these as compromised.

How do I remediate bnpl-blocks-desktop-bnpl-text-block if I installed it?

bnpl-blocks-desktop-bnpl-text-block is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed bnpl-blocks-desktop-bnpl-text-block — how do I know if it already compromised me?

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

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

Malicious package

bnpl-blocks-desktop-bnpl-text-blocknpm

bnpl-blocks-desktop-bnpl-text-block is a confirmed malicious npm package (MAL-2026-12944) that steals credentials and exfiltrates sensitive data (malicious version 35.9.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bnpl-blocks-desktop-bnpl-text-block (npm)

MAL-2026-12944

Immediate action

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

npm uninstall bnpl-blocks-desktop-bnpl-text-block

What this malware does

On require() of the package, platform.js selects a platform-specific endpoint and downloads an opaque binary from string-split obfuscated Cloudflare Workers hostnames (oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev), assembled at runtime from split fragments to evade static analysis. When HTTPS retrieval fails, it falls back to a DNS TXT-record covert channel under *.dl.wel1.ru (host assembled as ['sdk.d','l.','we','l1','.ru'].join('')), concatenating TXT chunks and base64-decoding them into an executable buffer. The payload is written to /tmp/.cache<hex> on Unix or %TEMP%/dotnet_diag_<hex>.exe on Windows (disguised as analytics/diagnostics state), chmod 0755, and detached-spawned via /bin/sh -c or cmd /c start. Cover-story telemetry-opt-out env var names (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) and diagnostics-shaped file names are present but do not alter the drop-and-execute behavior. Package name pattern (bnpl-blocks-desktop-bnpl-text-block) has no legitimate library content matching the advertised purpose.

Malicious versions

1 flagged

35.9.4

Indicators of compromise (SHA-256)

4073d41c6f9c313ea3c3e26c01e9d8de4032797e7d6e80e51c214eb37c1969f9

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bnpl-blocks-desktop-bnpl-text-block (version 35.9.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-desktop-bnpl-text-block across your stack and pipelines.
If you installed it — respond
bnpl-blocks-desktop-bnpl-text-block is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If bnpl-blocks-desktop-bnpl-text-block 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-desktop-bnpl-text-block 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-desktop-bnpl-text-block on npm has been identified as a malicious package (version 35.9.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015441

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-desktop-bnpl-text-block-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database