Which versions of bigops-products are malicious?

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

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

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

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

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

Malicious package

bigops-productsnpm

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

Malicious code in bigops-products (npm)

MAL-2026-13236

Immediate action

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

npm uninstall bigops-products

What this malware does

On require() of bigops-products, init.js downloads a platform-specific binary from Cloudflare Workers hosts whose names are assembled at runtime from string fragments (oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev), with a DNS-TXT covert-channel fallback that reconstructs a base64 payload from numbered subdomains of *.dl.wel1.ru (sdk/ext/pkg/net.dl.wel1.ru). The fetched binary is written to /tmp or %TEMP% under a cover name (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmod 755, then spawned detached via spawn("/bin/sh",["-c", path+" &"],{detached:true,stdio:"ignore"}).unref() (or spawn("cmd",...) on Windows). A marker file.analytics_state and env-var opt-outs (DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK) provide telemetry cover. Destination hostnames are constructed via array.join to defeat static string scans.

Malicious versions

1 flagged

35.7.4

Indicators of compromise (SHA-256)

62c972a30e05df0a94eb9aed3490a04da317cb450b64fd62a7183bca30afe573

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

Campaign

IN-MAL-2026-015762

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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