Which versions of bigops-statements-timeline are malicious?

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

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

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

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

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

Malicious package

bigops-statements-timelinenpm

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

Malicious code in bigops-statements-timeline (npm)

MAL-2026-13250

Immediate action

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

npm uninstall bigops-statements-timeline

What this malware does

On require() of the package, index.js loads support.js which selects a platform-specific asset path and downloads a binary over HTTPS from a rotating list of anonymous Cloudflare Workers subdomains (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev), with a DNS TXT chunked-base64 fallback under *.dl.wel1.ru. The fetched bytes are written to /tmp or %TEMP% under disguised names (analytics_state, dotnet_diag*), chmod 0755'd, and spawned detached via /bin/sh -c or cmd.exe /c start /b. Destination hostnames and fallback DNS domains are reconstructed at runtime from split string fragments joined via Array.join to defeat static analysis. Installing or requiring this package results in execution of arbitrary attacker-controlled native code on the installer's host.

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

Indicators of compromise (SHA-256)

d10168eeae00c6455a6a5a4838aa1afc9460a1edbc287d0b6f8b4acab5eae316

c1aeae83378291d53b6242b826950e4cdfb2b2cde419548feb846a2e1b1a6934

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

Campaign

IN-MAL-2026-015748GHSA-mrfg-393h-v67j

References

Credits

Amazon Inspector · finder

Detect & block this

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