bigops-status-selection (npm) · Malicious Code
Affects bigops-status-selectionSource GCVE Database
Malicious package : remove bigops-status-selection 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-13251
What to do
Remove bigops-status-selection 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-status-selection | 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 (00ac52845dd473e3c39d37b9f3916ed67f48cabfb276bc8cc2e9ca2dca401ce5) On require(), _bootstrap.js selects a platform-specific path, fetches a binary from one of three hardcoded *.workers.dev hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS TXT-record fallback channel over *.dl.wel1.ru subdomains, writes it to /tmp or %TEMP% under a disguised name (.cache_<tag> / dotnet_diag_<tag>.exe), chmods 0755, and detached-spawns it via /bin/sh -c or cmd /c start (_bootstrap.js line 119, 121, 125). Destination hostnames are split across array joins to evade static string search, and a secondary loader reassembles a base64 payload from indexed DNS TXT records (count from c.<domain>, chunks from <i>.<domain>). Cover-story comments frame the behavior as analytics/telemetry. ## Source: ghsa-malware (9e7caf9639d9018e9b2d1b267b2ac9aa3910b7c1554c960ac992a948d435b7ae) 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.