Which versions of bigops-storio are malicious?

The following npm versions of bigops-storio are flagged malicious: 35.8.7. Treat any of these as compromised.

How do I remediate bigops-storio if I installed it?

Remove bigops-storio 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.

I already installed bigops-storio — how do I know if it already compromised me?

If bigops-storio 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.

Is bigops-storio part of a known attack campaign?

Yes — bigops-storio is associated with the IN-MAL-2026-015746, GHSA-g548-9c3x-q2r5 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find bigops-storio across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-storio (version 35.8.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-storio across your stack and pipelines.

Malicious package

bigops-storionpm

bigops-storio is a confirmed malicious npm package (MAL-2026-13252) that executes malicious code on install (malicious version 35.8.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bigops-storio (npm)

MAL-2026-13252

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall bigops-storio

What this malware does

On require() of bigops-storio, _support.js selects a platform-specific endpoint and fetches an opaque binary over HTTPS from one of four string-split *.workers.dev hosts (oob-worker.cf100-416.workers.dev, cf101-adf, cf99-9b3, cf103-070 under workers.dev), assembled at runtime via array.join("") to hide the destinations from static inspection. The fetched bytes are written to /tmp or %TEMP% under a hidden random filename (dot-prefixed / dotnet_diag-style cover names), chmod 0755'd, and spawned detached via /bin/sh -c or cmd.exe /c start /b with stdio ignored. A DNS-TXT fallback (txtFetch/dns.resolveTxt against sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru — also assembled from string fragments) reassembles N base64-encoded TXT chunks into the same executable payload when HTTPS delivery fails. There is no version pinning, no hash or signature verification, and the fetched executable is unrelated to the package's stated storio abstraction purpose. The dropper runs automatically at library load time via index.js's try{require('./_support')}.

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

1 flagged

35.8.7

Indicators of compromise (SHA-256)

072daea48b555582ea01125b1a71fff5907e73bc890ec56f7b012ac38230b69e

cd9ebb4bf8d8e6554d93f8343675d991c677dea6469481d1689813b405dca59c

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-storio (version 35.8.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-storio across your stack and pipelines.
If you installed it — respond
Remove bigops-storio 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 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 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

No. bigops-storio on npm has been identified as a malicious package (version 35.8.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015746GHSA-g548-9c3x-q2r5

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-storio-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database