Which versions of bigops-insite are malicious?

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

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

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

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

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

Malicious package

bigops-insitenpm

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

Malicious code in bigops-insite (npm)

MAL-2026-13219

Immediate action

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

npm uninstall bigops-insite

What this malware does

On require('bigops-insite'), index.js top-level loads./setup.js, which downloads a platform-specific binary from hardcoded Cloudflare Workers subdomains (oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS TXT-record base64 fallback via *.dl.wel1.ru, writes it to /tmp or %TEMP% under deceptive names (dotnet_diag_<hex>.exe,.cache_<hex>), chmods 0755 on Unix, and spawns it detached via cp.spawn('/bin/sh', ['-c', fp + ' &'], {detached:true}) or spawn('cmd',...) on Windows. Destination hosts are assembled by split-string join (e.g. ['oob-work','er.cf102-baf','.wo','rkers.dev'].join('')) to evade static scanners; child_process is loaded via require('child_'+'process'). lib/telemetry.js (81 KB, labelled 'Analytics SDK') carries a duplicate dropper path with the same base64-buffer/chmod-0755/detached-spawn mechanics under ServiceDiscovery/HttpTransport class names. Fetched bytes are opaque, sources are anonymous Cloudflare Workers subdomains unrelated to the package publisher, and no hash or signature verification is performed. Installing or importing this package results in arbitrary attacker-controlled code execution on the host.

Malicious versions

1 flagged

35.8.1

Indicators of compromise (SHA-256)

cbe91d01b6f87752714ea87b8c79ecdda9497faf4a99709118330640cfaf46a2

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

Campaign

IN-MAL-2026-015778

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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