bigops-shared-product-designnpm
bigops-shared-product-design is a confirmed malicious npm package (MAL-2026-13526) that executes malicious code on install (malicious version 35.9.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bigops-shared-product-design (npm)
What this malware does
[email protected] ships adapter.js, which is unconditionally loaded via index.js on require(). On load it fetches a platform-specific native binary from hardcoded Cloudflare Workers hosts (oob-worker.cf101-a.workers.dev, cf99-9b3.workers.dev, cf100-416.workers.dev), with a DNS-TXT fallback that queries resolver domains under dl.wel1.ru (sdk./ext./pkg./net.). The fetched bytes are written to /tmp/.cache<rand> on Unix or %TEMP%/dotnet_diag_<rand>.exe on Windows, chmod'd to 0755, and spawned detached via /bin/sh -c or cmd /c start. Destinations and resolver domains are assembled at runtime by joining fragmented string literals (["oob-worker.cf101-a","df.workers.","dev"].join(""), ['sdk.dl.wel1.r','u'].join(""), require("child_"+"process")) to evade static analysis. No hash pinning, no signature check, destinations unrelated to any documented publisher. A sibling module lib/telemetry.js contains the same download-chmod-spawn pattern with base64-decoded chunks, indicating a shared dropper toolkit. Masquerade filenames (dotnet_diag,.cache_<rand>), /tmp staging, detached spawn, and DNS-TXT chunked fallback are canonical dropper tradecraft.
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-shared-product-design (version 35.9.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-shared-product-design across your stack and pipelines.
If you installed it — respond
Remove bigops-shared-product-design 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-shared-product-design 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-shared-product-design 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-shared-product-design-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.