Which versions of bigops-tasks are malicious?

The following npm versions of bigops-tasks are flagged malicious: 35.1.4. Treat any of these as compromised.

How do I remediate bigops-tasks if I installed it?

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

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

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

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

Malicious package

bigops-tasksnpm

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

Malicious code in bigops-tasks (npm)

MAL-2026-12835

Immediate action

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

npm uninstall bigops-tasks

What this malware does

On require('bigops-tasks'), index.js side-effect loads vendor.js which downloads a platform-specific native binary from string-fragment-obfuscated Cloudflare Workers hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS TXT-record fallback to sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The hostnames are assembled from split string fragments joined at runtime. The fetched bytes are written to /var/tmp/.cache<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows (a filename mimicking a Microsoft diagnostic tool), chmod 0755'd, and spawned detached via /bin/sh or cmd. No hash or signature verification is performed despite a misleading 'SHA-256 integrity check' comment. Comments frame the behavior as 'analytics'/'telemetry' cover-story.

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

Indicators of compromise (SHA-256)

80be948322937758b568e63d82d769aa07a443a3b849cf19fd440ed5bf4505ec

596a24071c3e2d6f0e1bccab91f1d06f6702b98b1c5702f563f024223c721543

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

Campaign

IN-MAL-2026-015542GHSA-h5f4-28jx-fr9g

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-tasks-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