Which versions of bnpl-blocks-playwright are malicious?

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

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

Remove bnpl-blocks-playwright 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-playwright — how do I know if it already compromised me?

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

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

Malicious package

bnpl-blocks-playwrightnpm

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

Malicious code in bnpl-blocks-playwright (npm)

MAL-2026-13012

Immediate action

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

npm uninstall bnpl-blocks-playwright

What this malware does

On require('bnpl-blocks-playwright'), index.js loads bridge.js which downloads a platform-specific binary from obfuscated Cloudflare Workers subdomains (oob-worker.cf10{0,1,2,3}-*.workers.dev, reassembled via array.join('')) with DNS TXT fallback to sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, writes it to /tmp or %TEMP% under a disguised name (dotnet_diag.exe,.cache_), chmod 0755s it on Unix, and spawns it detached via /bin/sh -c or cmd.exe. Hostnames and API identifiers (child_process, chmodSync) are split-concatenated at runtime to evade static analysis. The package is advertised as a Playwright/BNPL adapter and has no legitimate need to fetch and execute native binaries from anonymous Cloudflare Workers subdomains on import.

Malicious versions

1 flagged

35.4.6

Indicators of compromise (SHA-256)

b85856c1395372c88e148fdabb77be27f0556ad68ba3eb7f5c62d063a9154607

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-playwright (version 35.4.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bnpl-blocks-playwright across your stack and pipelines.
If you installed it — respond
Remove bnpl-blocks-playwright 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-playwright 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-playwright 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-playwright on npm has been identified as a malicious package (version 35.4.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015370

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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