Which versions of bigops-security are malicious?

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

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

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

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

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

Malicious package

bigops-securitynpm

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

Malicious code in bigops-security (npm)

MAL-2026-13525

Immediate action

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

npm uninstall bigops-security

What this malware does

On require('bigops-security'), index.js loads bridge.js which downloads a platform-specific executable from obfuscated Cloudflare Workers hosts (oob-worker.cf10{0..3}-*.workers.dev) with a DNS-TXT chunked-base64 fallback via *.dl.wel1.ru subdomains. Destination hostnames are reconstructed at runtime from split string arrays (e.g. ['sdk','.dl.','wel1.','ru'].join('')) rather than appearing as plain literals. The fetched bytes are written to /tmp or %TEMP% under disguised names such as dotnet_diag<hex>.exe and.cache_<hex>, chmod 755'd, and detach-spawned via spawn('/bin/sh',...) or spawn('cmd',...) at _bridge.js:121-127. Cover-story identifiers ("analytics", "telemetry", "CDN", "Respect opt-out") frame the code as benign while the actual behavior is fetch-and-execute of an opaque binary from author-controlled infrastructure. No native-build purpose is present in the tarball; the package advertises itself as a security module.

Malicious versions

1 flagged

35.8.8

Indicators of compromise (SHA-256)

f4eccfe477123e2d048f10c141165dec00f0ce2bfe28b7b9611a189fc63f0384

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

Campaign

IN-MAL-2026-016968

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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