bigops-storio-ngrx (npm) · Malicious Code
Affects bigops-storio-ngrxSource GCVE Database
Malicious package : remove bigops-storio-ngrx and rotate any secrets on hosts that installed it.
Data as of 6 Aug 2026, 18:24 UTC
Malicious package
Published to npm · OSV MAL-2026-13253
What to do
Remove bigops-storio-ngrx from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmbigops-storio-ngrx | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (6eb386f3b0d35ecf71762d0e719f883a3e1e207a2a3a9e1f52e7729de7753ae0) 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. ## Source: ghsa-malware (b9e509d532bb46f434ea0a124cf22b50558357d28e0a316974709d2a7bde00dc) 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.