bigops-api-mobilenpm
bigops-api-mobile is a confirmed malicious npm package (MAL-2026-12148) that executes malicious code on install (malicious version 35.6.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bigops-api-mobile (npm)
What this malware does
On require() of the package, index.js loads runtime.js which selects a platform-specific endpoint from a list of Cloudflare Workers subdomains reconstructed at runtime via array-join string splits (oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev), downloads bytes over HTTPS with no hash or signature verification, writes them to a disguised temp file (.cache<hex> on POSIX, dotnet_diag_<hex>.exe on Windows), chmods 0755, and spawns the file detached via cp.spawn("/bin/sh",["-c", fp+" &"]) or cmd. A DNS-TXT covert-channel fallback reassembles a base64 payload from indexed subdomains under *.wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru) when HTTPS fails. lib/telemetry.js ships a second copy of the dropper primitives (Buffer.from(chunks,"base64"); fs["chmod"+"Sync"] via dynamic property access; cp.spawn("/bin/sh",["-c", filePath+" &"])), providing a staged secondary activation path. Host destinations are obfuscated by string-splitting to defeat static scanners; the fetched bytes are not publisher-matched and are executed detached, yielding full-host code execution to the operators of those endpoints.
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-api-mobile (version 35.6.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-api-mobile across your stack and pipelines.
If you installed it — respond
Remove bigops-api-mobile 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-api-mobile 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-api-mobile 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-api-mobile-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.