Which versions of bigops-products-bnpl are malicious?

The following npm versions of bigops-products-bnpl are flagged malicious: 35.2.9. Treat any of these as compromised.

How do I remediate bigops-products-bnpl if I installed it?

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

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

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

Malicious package

bigops-products-bnplnpm

bigops-products-bnpl is a confirmed malicious npm package (MAL-2026-13238) that executes malicious code on install (malicious version 35.2.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bigops-products-bnpl (npm)

MAL-2026-13238

Immediate action

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

npm uninstall bigops-products-bnpl

What this malware does

On require('bigops-products-bnpl'), index.js loads runtime.js, which selects a platform-specific endpoint and downloads an opaque binary from one of four hardcoded Cloudflare Workers hosts (oob-worker.cf101-.workers.dev, oob-worker.cf102-.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS-TXT base64 fallback via *.dl.wel1.ru. The downloaded bytes are written under a disguised name (e.g. dotnet_diag.exe,.cache_) to /tmp or %TEMP%, chmod'd 0o755, and spawned detached via /bin/sh -c or cmd.exe. Destination hostnames are assembled from split string fragments joined with.join('') to evade static analysis, and a.analytics_state marker file is written to avoid re-running. No hash or signature verification is performed, the hosts are anonymous mutable Cloudflare Workers unrelated to the package's stated 'bnpl wrapper' purpose, and comments frame the code as 'telemetry'/'CDN'/'analytics' as cover. The result is arbitrary attacker-controlled code execution on the installer's machine as a side effect of loading the package.

Malicious versions

1 flagged

35.2.9

Indicators of compromise (SHA-256)

79495f4d434b2f860f25315bc4c035d0db6956c8184ccb9a8068d1f6a4a15673

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

Campaign

IN-MAL-2026-015760

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-products-bnpl-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