bigops-storio-store-adapternpm
bigops-storio-store-adapter is a confirmed malicious npm package (MAL-2026-13256) that executes malicious code on install (malicious version 35.9.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bigops-storio-store-adapter (npm)
What this malware does
On require of the package, index.js loads bridge.js which selects a platform-specific binary path and downloads an opaque native binary from author-controlled Cloudflare Workers hosts whose names are reconstructed at runtime by array-join to evade static analysis (oob-worker.cf99-9b3.workers.dev, cf101-adf.workers.dev, cf103-070.workers.dev), with a DNS-TXT chunk fallback under *.dl.wel1.ru. The binary is written under /var/tmp or %TEMP% with cover-story filenames (dotnet_diag<hex>.exe,.cache_<hex>), chmod 0755'd, and detached-spawned via cmd.exe/start or /bin/sh -c. A cache stamp under /tmp/.analytics_* is used to avoid re-execution. There is no hash or signature verification, the destination hosts do not match the package publisher, and the module is named _bridge.js with cover-story identifiers (analytics_state, dotnet_diag). An additional 81KB lib/telemetry.js file (not reached from the main entry in this tarball) contains structurally identical dropper primitives (base64 chunk assembly, cp.spawn('/bin/sh',['-c', filePath+' &']), chmodSync 0755, ServiceDiscovery/WorkerHost classes) as a reserve/variant payload.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
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-storio-store-adapter (version 35.9.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-storio-store-adapter across your stack and pipelines.
If you installed it — respond
Remove bigops-storio-store-adapter 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-storio-store-adapter 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-storio-store-adapter 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-storio-store-adapter-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.