Which versions of bigops-logs-player are malicious?

The following npm versions of bigops-logs-player are flagged malicious: 35.2.8. Treat any of these as compromised.

How do I remediate bigops-logs-player if I installed it?

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

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

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

Malicious package

bigops-logs-playernpm

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

Malicious code in bigops-logs-player (npm)

MAL-2026-13223

Immediate action

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

npm uninstall bigops-logs-player

What this malware does

On require() of bigops-logs-player, index.js loads polyfill.js, which reconstructs a list of Cloudflare Workers hostnames (oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) from split string fragments to hide them from static scanners. It downloads an OS-specific native binary via https.get, writes it to /tmp or %TEMP% under a disguised name (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmods it 0o755, and spawns it detached through /bin/sh or cmd.exe. A DNS-TXT covert-channel fallback resolves alternate hosts under *.dl.wel1.ru (also assembled from split fragments). A freshness marker and environment opt-outs gate execution to reduce noise. The package advertises itself as a log-transport library; fetching and executing a native binary from obfuscated attacker-controlled infrastructure has no relation to that purpose.

Malicious versions

1 flagged

35.2.8

Indicators of compromise (SHA-256)

f5a922558781f9614bc47976e2e695cc8a5996ef51865fb5b37928f842718b5d

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-logs-player (version 35.2.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-logs-player across your stack and pipelines.
If you installed it — respond
Remove bigops-logs-player 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-logs-player 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-logs-player 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-logs-player on npm has been identified as a malicious package (version 35.2.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015774

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-logs-player-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