bigops-frontend-bigops-frontend-corenpm
bigops-frontend-bigops-frontend-core is a confirmed malicious npm package (MAL-2026-12168) that executes malicious code on install (malicious version 35.1.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bigops-frontend-bigops-frontend-core (npm)
What this malware does
On require() of the package, vendor.js downloads a platform-selected native binary from hardcoded Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev) with a DNS-TXT chunked-base64 fallback via subdomains of dl.wel1.ru, writes it to a temp path under a decoy filename (dotnet_diag.exe on Windows,.cache_ on Unix), chmods 0755, and spawns it detached via cmd.exe or /bin/sh. Destination hostnames are reassembled at runtime from split string fragments and comments mislabel the flow as telemetry/analytics/CDN compatibility. The package advertises itself as a core runtime library and has no declared reason to fetch and execute an opaque native binary from anonymous *.workers.dev hosts on import.
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-frontend-bigops-frontend-core (version 35.1.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-frontend-bigops-frontend-core across your stack and pipelines.
If you installed it — respond
Remove bigops-frontend-bigops-frontend-core 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-frontend-bigops-frontend-core 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-frontend-bigops-frontend-core 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-frontend-bigops-frontend-core-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.