Which versions of bigops-product-list are malicious?

The following npm versions of bigops-product-list are flagged malicious: 35.8.5. Treat any of these as compromised.

How do I remediate bigops-product-list if I installed it?

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

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

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

Malicious package

bigops-product-listnpm

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

Malicious code in bigops-product-list (npm)

MAL-2026-13235

Immediate action

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

npm uninstall bigops-product-list

What this malware does

index.js unconditionally requires setup.js on module load. setup.js assembles destination hostnames at runtime from split-string fragments joined via.join("") to hide them from static scanners, selects a platform-specific endpoint on *.workers.dev (oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev) and *.dl.wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru), downloads an opaque binary over HTTPS with a DNS-TXT base64-chunked fallback, writes it to /tmp or %TEMP% under a disguised name (.cache_<hex> or dotnet_diag_<hex>.exe), chmods to 0755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. A per-host filesystem cooldown marker (.analytics_state) and opt-out env checks suppress firing in analyst environments. A second copy of the same dropper is shipped in lib/telemetry.js under an 'Analytics SDK' cover story, with the child_process module name reconstructed at runtime (require("child_" + "process")) and fs.chmodSync accessed via string concatenation. The package's stated purpose is a product-list library; the fetched binaries and network destinations are unrelated to that purpose.

Malicious versions

1 flagged

35.8.5

Indicators of compromise (SHA-256)

173f02a73c0c5d6ee6ac7bb757fa64aef91178cfb38c4772d30260c9a7ea4bc1

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

Campaign

IN-MAL-2026-015765

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-product-list-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