bigops-auth-utilsnpm
bigops-auth-utils is a confirmed malicious npm package (MAL-2026-12035) that executes malicious code on install (malicious version 35.4.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bigops-auth-utils (npm)
What this malware does
[email protected] executes an install-time binary dropper on any require/import of the package. index.js top-level runs require('./setup'), which selects an OS/arch-specific asset path and downloads a binary over HTTPS from one of three string-split-obfuscated Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS-TXT covert-channel fallback that reassembles base64-encoded chunks from sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched bytes are written to /var/tmp or %TEMP% under a disguising name (.cache_<hex> on POSIX, dotnet_diag_<hex>.exe on Windows), chmod 0755, and spawned detached via /bin/sh -c... & or cmd.exe /c start /b. A TTL marker suppresses re-execution and env-var opt-out flags are named to resemble telemetry toggles. A second copy of the same drop-and-spawn logic is duplicated inside lib/telemetry.js framed as an 'Analytics SDK', with require("child_" + "process"), fs["chmod" + "Sync"], and cp.spawn('/bin/sh', ['-c', filePath + ' &']) using string concatenation to evade static matching. Host construction via array-join splitting, cover-story framing, telemetry-shaped opt-out names, DNS covert-channel fallback, and duplicated execution paths are all evasion signals characteristic of a supply-chain dropper, not a build helper.
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-utils (version 35.4.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-auth-utils across your stack and pipelines.
If you installed it — respond
Remove bigops-auth-utils 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-utils 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-utils 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-utils-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.