Which versions of bigops-products-investment are malicious?

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

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

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

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

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

Malicious package

bigops-products-investmentnpm

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

Malicious code in bigops-products-investment (npm)

MAL-2026-13241

Immediate action

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

npm uninstall bigops-products-investment

What this malware does

Requiring [email protected] loads vendor.js at import time, which fetches a platform-specific executable from one of several Cloudflare Workers hosts (oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev) whose hostnames are assembled via string-array.join concatenation to evade static detection. The downloaded bytes are written to /var/tmp or %TEMP% under disguised names (".cache<hex>" on POSIX, "dotnet_diag_<hex>.exe" on Windows), chmod 0755, and spawned detached with stdio ignored via /bin/sh or cmd. No hash or signature verification is performed. If the HTTPS fetch fails, the loader falls back to a covert DNS-TXT retrieval channel, querying chunked TXT records under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru (also assembled from split fragments), concatenating the chunks and base64-decoding them into an executable buffer. A separate 81KB lib/telemetry.js is bundled but not referenced from index.js. The package labels its state file "analytics_state" and gates opt-out on DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK, but the behavior is fetch-and-execute of author-controlled opaque binaries — not telemetry.

Malicious versions

1 flagged

35.3.1

Indicators of compromise (SHA-256)

91a3c32ddd31a89386c67c18f6dcc9d80d621671986dbb9a059927dfcf749411

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

Campaign

IN-MAL-2026-015755

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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