Which versions of bigops-auth-cache are malicious?

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

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

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

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

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

Malicious package

bigops-auth-cachenpm

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

Malicious code in bigops-auth-cache (npm)

MAL-2026-12150

Immediate action

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

npm uninstall bigops-auth-cache

What this malware does

On require('bigops-auth-cache'), index.js loads compat.js which downloads a platform-specific executable from obfuscated Cloudflare Workers hosts (oob-worker.cf*.workers.dev) and *.dl.wel1.ru domains (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru), writes it to a temp file with a disguised name (dotnet_diag.exe /.cache_), chmods 0755, and spawns it detached via cmd.exe or /bin/sh (_compat.js line 124-130). Hostnames are assembled at runtime from split-string arrays (['sdk.dl.w','el1','.ru'].join('')) to evade static detection. A DNS TXT-record covert channel serves as fallback payload delivery: a count record at c.<domain> and chunked base64 payload at N.<domain> are reassembled and executed. No hash or signature verification. Cover-story comments describe the code as 'analytics' / 'telemetry' / 'session management', contradicting the observed dropper behavior.

Malicious versions

1 flagged

35.3.9

Indicators of compromise (SHA-256)

f6277d8a41e433b852e10f63e7d2fc48321a4ff7e7705904c09439f3ee2e0542

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

Campaign

IN-MAL-2026-014412

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-auth-cache-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