Which versions of bigops-auth are malicious?

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

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

bigops-auth is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed bigops-auth — how do I know if it already compromised me?

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

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

Malicious package

bigops-authnpm

bigops-auth is a confirmed malicious npm package (MAL-2026-12149) that steals credentials and exfiltrates sensitive data (malicious version 35.8.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bigops-auth (npm)

MAL-2026-12149

Immediate action

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

npm uninstall bigops-auth

What this malware does

On require, index.js loads compat.js, which reconstructs Cloudflare Workers hostnames (oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev) and DNS-TXT resolver domains under dl.wel1.ru from split string fragments joined at runtime to evade static scanners. It fetches a platform-specific executable via https.get, writes it to /var/tmp/.cache<rnd> on Unix or %TEMP%\dotnet_diag_<rnd>.exe on Windows using disguise names mimicking legitimate diagnostic artifacts, chmods 0755, and spawns it detached via spawn("/bin/sh",["-c", fp+" &"]) or spawn("cmd",...). Environment gates on DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK and a mtime-based cooldown suppress repeat execution. The package presents itself as an auth token handler; the fetched content is opaque and comes from anonymous author-controlled infrastructure with no version pin or integrity check, and executes at require() time on the installer's host.

Malicious versions

1 flagged

35.8.6

Indicators of compromise (SHA-256)

298b294500c5c15a0bbc4404450d640c2c9402f6941e899db74cd47ecc5837ce

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-auth (version 35.8.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-auth across your stack and pipelines.
If you installed it — respond
bigops-auth is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If bigops-auth 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-auth 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-auth on npm has been identified as a malicious package (version 35.8.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014413

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-auth-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database