bigops-timeline-uinpm
Advisory published Updated
bigops-timeline-ui is a confirmed malicious npm package (MAL-2026-12845) that executes malicious code on install (malicious version 35.5.8). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bigops-timeline-ui (npm)
What this malware does
On require() of bigops-timeline-ui, index.js loads./adapter.js which fetches a platform-specific binary from Cloudflare Workers hosts whose names are assembled at runtime from split string fragments (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS TXT-record fallback channel under *.dl.wel1.ru that reassembles a base64-encoded binary from numbered subdomain lookups. The fetched bytes are written to a hidden temp file using cover-story names (.cache<hex> on POSIX, dotnet_diag_<hex>.exe on Windows), chmod 0755 is applied, and the file is spawned detached via /bin/sh -c or cmd.exe /c start. There is no version pinning, no hash or signature verification, and the destinations are unrelated to any documented publisher for a timeline UI package. Runtime hostname construction and the DNS TXT transport are anti-analysis measures rather than legitimate delivery mechanisms.
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-timeline-ui (version 35.5.8).
If you installed it — respond
Remove bigops-timeline-ui 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-ui 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-timeline-ui-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.