bigops-statements-timelinenpm
Advisory published Updated
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)
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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for bigops-statements-timeline (version 35.2.4).
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 installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
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.