bigops-auth-interceptornpm
bigops-auth-interceptor is a confirmed malicious npm package (MAL-2026-12151) that executes malicious code on install (malicious version 35.7.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bigops-auth-interceptor (npm)
What this malware does
On require() of [email protected], index.js loads vendor.js which selects a platform-specific binary URL, downloads bytes over HTTPS from one of four string-concatenation-obfuscated Cloudflare Workers mirrors (oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev), writes them to a temp path under a disguised name (dotnet_diag<hex>.exe on Windows,.cache_<hex> on Linux), chmods 0755, and spawns the file detached via /bin/sh -c or cmd.exe. A DNS TXT-record fallback channel (c.<domain> returns a chunk count, then i.<domain> TXT records are concatenated and base64-decoded into the payload) is implemented against sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru, providing covert payload retrieval when HTTPS is blocked. A run-once marker file (.analytics_state) prevents repeated execution. Destination hosts are unrelated to any legitimate publisher of the package's stated purpose; the fetched bytes are unpinned, unsigned, and platform-selected.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-auth-interceptor (version 35.7.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-auth-interceptor across your stack and pipelines.
If you installed it — respond
Remove bigops-auth-interceptor 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-interceptor 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-interceptor 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks bigops-auth-interceptor-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.