Which versions of bigops-storio-ngrx are malicious?

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

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

bigops-storio-ngrx is a typosquat — you almost certainly intended a legitimately-named package. Remove bigops-storio-ngrx, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

If bigops-storio-ngrx 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-ngrx part of a known attack campaign?

Yes — bigops-storio-ngrx is associated with the IN-MAL-2026-015741, GHSA-v9j9-x22c-rgjq 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-ngrx 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-ngrx (version 35.2.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-storio-ngrx across your stack and pipelines.

Malicious package

bigops-storio-ngrxnpm

bigops-storio-ngrx is a confirmed malicious npm package (MAL-2026-13253) that typosquats a legitimate package to trick installs (malicious version 35.2.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bigops-storio-ngrx (npm)

MAL-2026-13253

Immediate action

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

npm uninstall bigops-storio-ngrx

What this malware does

On require(), index.js loads./ext.js which selects a per-OS asset path and downloads a binary payload from one of three runtime-assembled Cloudflare Workers hosts (oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS TXT covert-channel fallback that reassembles a base64 payload from numbered subdomains under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched bytes are written to /var/tmp/.cache<rand> on Unix or %TEMP%\dotnet_diag_<rand>.exe on Windows, chmod 0755, and spawned detached via spawn("/bin/sh", ["-c", path + " &"]) or spawn("cmd",...). Host strings are constructed via array-split.join("") to evade static inspection, and there is no hash or signature verification. Staging paths mimic system diagnostics names to blend in.

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.2.2

Indicators of compromise (SHA-256)

6eb386f3b0d35ecf71762d0e719f883a3e1e207a2a3a9e1f52e7729de7753ae0

b9e509d532bb46f434ea0a124cf22b50558357d28e0a316974709d2a7bde00dc

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-storio-ngrx (version 35.2.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-storio-ngrx across your stack and pipelines.
If you installed it — respond
bigops-storio-ngrx is a typosquat — you almost certainly intended a legitimately-named package. Remove bigops-storio-ngrx, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If bigops-storio-ngrx 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-ngrx 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-ngrx on npm has been identified as a malicious package (version 35.2.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015741GHSA-v9j9-x22c-rgjq

References

Credits

Amazon Inspector · finder

Detect & block this

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