bigops-products-timeline-commonsnpm
bigops-products-timeline-commons is a confirmed malicious npm package (MAL-2026-13246) that typosquats a legitimate package to trick installs (malicious version 35.1.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bigops-products-timeline-commons (npm)
What this malware does
The package advertises itself as shared primitive types with a trivial no-op class in index.js, but index.js unconditionally require()s loader.js, whose top-level bootstrap runs on any import. The loader assembles hostnames from split string fragments joined at runtime to hide them from static scanners, resolving to Cloudflare Workers subdomains such as oob-worker.cf99-9b3.workers.dev, with additional *.dl.wel1.ru fallbacks and a DNS TXT-record chunked download channel as covert transport. It selects a platform-specific binary (linux_x64, linux_arm64, darwin, win32), downloads it over HTTPS without pinning, hash, or signature verification, writes it to /var/tmp or %TEMP% under disguised names impersonating legitimate tooling (dotnet_diag<hex>.exe on Windows,.cache_<hex> or.analytics_state on Unix), chmods it 0o755, and spawns it detached via /bin/sh -c or cmd with unref(). The library API surface is a decoy for this import-time loader side effect. The combination of unconditional import-time execution, obfuscated attacker-controlled destinations, DNS covert-channel fallback, disguised filenames, and unverified remote binary execution matches an install/import-time RCE dropper.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-products-timeline-commons (version 35.1.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-products-timeline-commons across your stack and pipelines.
If you installed it — respond
bigops-products-timeline-commons is a typosquat — you almost certainly intended a legitimately-named package. Remove bigops-products-timeline-commons, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If bigops-products-timeline-commons 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-products-timeline-commons 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks bigops-products-timeline-commons-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.