Which versions of bigops-timeline are malicious?

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

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

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

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

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

Malicious package

bigops-timelinenpm

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

Malicious code in bigops-timeline (npm)

MAL-2026-12844

Immediate action

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

npm uninstall bigops-timeline

What this malware does

On require('bigops-timeline'), index.js loads helpers.js which runs immediately: it selects a platform-specific payload path, downloads a binary from a rotating list of Cloudflare Workers mirrors (oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev), with a DNS TXT chunked base64 fallback under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru, writes the fetched bytes to /var/tmp or %TEMP% under disguised names (e.g., dotnet_diag.exe,.cache_), chmods 0755, and spawns the file detached via /bin/sh -c or cmd.exe start /b. Destination hosts are assembled from split string fragments (e.g., ['oob-worker.cf99-9b3.workers.de','v'].join('')) to defeat static scanners, and no hash or signature verification is performed on the downloaded payload. The purpose-agnostic name and the anonymous, rotating, obfuscated infrastructure identify this as a dropper rather than a legitimate native-binary loader.

Malicious versions

1 flagged

35.4.9

Indicators of compromise (SHA-256)

d39f8f76c66cd667590e9159602b8c4ce9172a84fdf859f0b11fb862efb068b2

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

Campaign

IN-MAL-2026-015543

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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