What does the bigops-status-selection malware do?

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_ / dotnet_diag_ .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. , chunks from .<doma

Which versions of bigops-status-selection are malicious?

The following npm versions of bigops-status-selection are flagged malicious: 35.3.2. Treat any of these as compromised.

How do I remediate bigops-status-selection if I installed it?

Remove bigops-status-selection 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-status-selection — how do I know if it already compromised me?

If bigops-status-selection was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is bigops-status-selection part of a known attack campaign?

Yes — bigops-status-selection is associated with the IN-MAL-2026-015749, GHSA-r2qr-xq83-5p7q 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-status-selection across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bigops-status-selection (version 35.3.2).

Malicious package

bigops-status-selectionnpm

Advisory published Aug 5, 2026Updated Aug 6, 2026

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

Malicious code in bigops-status-selection (npm)

MAL-2026-13251

Immediate action

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

npm uninstall bigops-status-selection

What this malware does

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.

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

Indicators of compromise (SHA-256)

00ac52845dd473e3c39d37b9f3916ed67f48cabfb276bc8cc2e9ca2dca401ce5

9e7caf9639d9018e9b2d1b267b2ac9aa3910b7c1554c960ac992a948d435b7ae

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for bigops-status-selection (version 35.3.2).
If you installed it — respond
Remove bigops-status-selection 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-status-selection was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-015749GHSA-r2qr-xq83-5p7q

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-status-selection-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