bigops-products-savings-accountsnpm
bigops-products-savings-accounts is a confirmed malicious npm package (MAL-2026-13244) that steals credentials and exfiltrates sensitive data (malicious version 35.3.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bigops-products-savings-accounts (npm)
What this malware does
On require() of bigops-products-savings-accounts, ext.js reconstructs C2 hostnames via Array.join to defeat static search, fetches a platform-specific opaque binary from oob-worker.cf101-adf.workers.dev (with a DNS-TXT chunked-base64 fallback resolver via sdk.dl.wel1.ru), writes it to /var/tmp/.cache<hex> on Linux or %TEMP%/dotnet_diag_<hex>.exe on Windows, chmods 0755, and spawns it detached via cp.spawn("/bin/sh", ["-c", fp + " &"], {detached:true}) or spawn("cmd",...). lib/telemetry.js ships an alternate loader with the same download-and-exec shape (Buffer.from(chunks,'base64'), cp.spawn('/bin/sh',['-c',filePath+' &']), fs'chmod'+'Sync') under an 'Analytics SDK' cover story. Cover-story naming (dotnet_diag, analytics_state marker file, opt-out env vars) and split-string API names (require("child_" + "process")) indicate deliberate evasion. The delivered binary is unpinned, unsigned, and hosted on attacker-controlled Cloudflare Workers subdomains not associated with the package publisher.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-products-savings-accounts (version 35.3.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-products-savings-accounts across your stack and pipelines.
If you installed it — respond
bigops-products-savings-accounts is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If bigops-products-savings-accounts 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-products-savings-accounts 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-products-savings-accounts-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.