bigops-awesome-viewernpm
bigops-awesome-viewer is a confirmed malicious npm package (MAL-2026-12153) that executes malicious code on install (malicious version 35.1.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bigops-awesome-viewer (npm)
What this malware does
index.js unconditionally require()s./loader on module load. loader.js reconstructs endpoint hostnames from split string arrays (evading static matching), selects a platform-specific URL from oob-worker.cf101-adf.workers.dev / oob-worker.cf102-baf.workers.dev / oob-worker.cf103-070.workers.dev, and falls back to a chunked base64 DNS-TXT channel over sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru when HTTPS fails. The fetched opaque binary is written to /var/tmp/.cache<hex> on Unix (or %TEMP%/dotnet_diag<hex>.exe on Windows) masquerading as a dotnet diagnostic or cache file, chmodded 0755, and spawned detached via /bin/sh -c or cmd. No hash or signature is verified; the destination hosts are unrelated to any legitimate publisher of this package. A marker file /tmp/.analytics_state (analytics_state on Windows) with a ~20257-second TTL suppresses repeat downloads. lib/telemetry.js ships a second copy of the drop-and-exec primitives (Buffer.from(chunks,'base64'), fs['chmod'+'Sync'](path, 0o755), cp.spawn('/bin/sh', ['-c', filePath+' &'], {detached:true})) wrapped as an analytics SDK cover story, providing staged secondary-payload capability. Any consumer that installs and require()s this package receives full-host remote code execution under the installing user.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-awesome-viewer (version 35.1.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-awesome-viewer across your stack and pipelines.
If you installed it — respond
Remove bigops-awesome-viewer 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-awesome-viewer 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-awesome-viewer 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-awesome-viewer-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.