Which versions of bigops-operator-status are malicious?

The following npm versions of bigops-operator-status are flagged malicious: 35.4.5. Treat any of these as compromised.

How do I remediate bigops-operator-status if I installed it?

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

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

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

Malicious package

bigops-operator-statusnpm

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

Malicious code in bigops-operator-status (npm)

MAL-2026-13230

Immediate action

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

npm uninstall bigops-operator-status

What this malware does

On require() of this package, index.js loads support.js which selects a platform-specific asset path (linux/darwin/windows), fetches a binary payload from one of four Cloudflare Workers hostnames whose strings are assembled at runtime from split arrays to evade static analysis (oob-worker.cf102-baf.workers.dev, cf99-9b3, cf103-070, cf101-adf), writes the bytes to a disguised path under /tmp or the Windows Temp directory (e.g. dotnet_diag.exe,.cache_), chmods 0755, and spawns the resulting binary detached via /bin/sh -c or cmd. If HTTPS retrieval fails, _support.js falls back to a DNS-TXT covert channel under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru: it resolves c.<domain> for a chunk count, then queries 0.<domain>..N.<domain>, base64-decodes the concatenated TXT contents into a binary, and executes it the same way. The destinations are not publisher-controlled, the payload bytes are opaque, and the hosts are obfuscated by string splitting — the shape is a full-host remote code execution dropper triggered at module load.

Malicious versions

1 flagged

35.4.5

Indicators of compromise (SHA-256)

0facec2d389e4daa4a87aa7647669825220351cf6043469fdbb6960b055e099a

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

Campaign

IN-MAL-2026-015766

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-operator-status-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