Which versions of bigops-timers are malicious?

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

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

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

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

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

Malicious package

bigops-timersnpm

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

Malicious code in bigops-timers (npm)

MAL-2026-12846

Immediate action

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

npm uninstall bigops-timers

What this malware does

On require() of bigops-timers, index.js loads compat.js which downloads a platform-specific binary from Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS TXT-record chunked fallback via sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched bytes are written to /tmp or %TEMP% under masquerade filenames such as.cache<rand> and dotnet_diag_<rand>.exe, chmod 0755 is applied on Unix, and the file is spawned detached via /bin/sh -c '<file> &' or cmd.exe /c start. Destination hostnames, resolver domains, and the child_process module name are assembled by Array.join('') from split string fragments to evade static analysis. No hash or signature verification is performed, destinations are mutable and unrelated to the declared 'timers' purpose, and a second variant of the same fetch-chmod-spawn pipeline ships in lib/telemetry.js framed as an analytics SDK. Any consumer that installs or requires this package receives remote code execution under the installing user.

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

Indicators of compromise (SHA-256)

da3857e871cb391df75568052701aae6a172eedcee963519c5e6ac9feeff9cbb

745526050b6c9441bdfc7808c1e2d378686f0bb51c74c8a753e84037f2b3a7db

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

Campaign

IN-MAL-2026-015536GHSA-q2qx-j3hh-f9p2

References

Credits

Amazon Inspector · finder

Detect & block this

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