Which versions of bnpl-blocks-data-schema-generator are malicious?

The following npm versions of bnpl-blocks-data-schema-generator are flagged malicious: 35.2.1. Treat any of these as compromised.

How do I remediate bnpl-blocks-data-schema-generator if I installed it?

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

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

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

Malicious package

bnpl-blocks-data-schema-generatornpm

bnpl-blocks-data-schema-generator is a confirmed malicious npm package (MAL-2026-12909) that executes malicious code on install (malicious version 35.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bnpl-blocks-data-schema-generator (npm)

MAL-2026-12909

Immediate action

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

npm uninstall bnpl-blocks-data-schema-generator

What this malware does

index.js unconditionally requires bootstrap.js, which on module load reconstructs Cloudflare Workers subdomains (oob-worker.cf10x-xxx.workers.dev) and *.dl.wel1.ru hosts from split string fragments, fetches a platform-specific executable via https.get with a DNS-TXT fallback that reassembles base64 chunks from numbered subdomains, writes the payload to a temp path under disguised names (e.g. dotnet_diag.exe,.cache_), chmods 0755 on Unix, and spawns it detached via /bin/sh -c or cmd.exe /c start. A second file lib/telemetry.js labelled as a telemetry SDK contains the same write+chmod+spawn primitives (Buffer.from(chunks,'base64'), cp.spawn('/bin/sh',['-c', filePath+' &']), fs['chmod'+'Sync'](extensionPath, 0755)) as a redundant dropper. The behavior fires whenever any consumer require()s the package, giving arbitrary remote code execution on the installer's host.

Malicious versions

1 flagged

35.2.1

Indicators of compromise (SHA-256)

b1e39c2d94a6114333c4275444d786188f00056a96e6e6296cd3abf275e3d5bc

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

Campaign

IN-MAL-2026-015469

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bnpl-blocks-data-schema-generator-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