NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

bigops-auth-interceptornpm

Advisory published Updated

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)

MAL-2026-12151
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bigops-auth-interceptor

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.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
35.7.2

Indicators of compromise (SHA-256)

018aa5e99b7e6aa9f438b51ee00164801a2eb1c52e78ad123d0c490dced4b67c
6b77a5b2ba5b6c81e51ed296239e78e146e052a7cc4860a48d992932aa47140a

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for bigops-auth-interceptor (version 35.7.2).

  2. 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.

  3. Did it already run?

    If bigops-auth-interceptor was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. bigops-auth-interceptor on npm has been identified as a malicious package (version 35.7.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014404GHSA-7pp9-3qqc-vc84

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.

Explore

bigops-auth-interceptor (npm) malicious package — MAL-2026-12151 | O3 Security