bigops-auth-provider-interceptornpm
bigops-auth-provider-interceptor is a confirmed malicious npm package (MAL-2026-12152) that typosquats a legitimate package to trick installs (malicious version 35.8.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bigops-auth-provider-interceptor (npm)
What this malware does
On require, bigops-auth-provider-interceptor loads init.js, which reconstructs destination hostnames via string-split/join (oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, and fallback sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru), selects a platform-specific binary for Linux/macOS/Windows, downloads it over HTTPS with a DNS-TXT chunked-base64 fallback channel, writes it to /var/tmp/.cache<rand> or %TEMP%\dotnet_diag_<rand>.exe, sets mode 0755, and spawns it detached via /bin/sh -c or cmd. lib/telemetry.js ships a second copy of the same download-decode-chmod-spawn chain with additional string concatenation obfuscation on the child_process require and chmod call. The hostnames are unrelated to the package's declared purpose, no version pin or hash verification is performed, the binary is staged to a hidden dot-file or a filename impersonating a Microsoft.NET diagnostic tool, and execution is detached to survive the installing process. This fires on any require of the package.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-auth-provider-interceptor (version 35.8.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-auth-provider-interceptor across your stack and pipelines.
If you installed it — respond
bigops-auth-provider-interceptor is a typosquat — you almost certainly intended a legitimately-named package. Remove bigops-auth-provider-interceptor, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If bigops-auth-provider-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-provider-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-provider-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.