bigops-legacy-telephony-panelnpm
bigops-legacy-telephony-panel is a confirmed malicious npm package (MAL-2026-13221) that steals credentials and exfiltrates sensitive data (malicious version 35.5.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bigops-legacy-telephony-panel (npm)
What this malware does
On require of this package, index.js loads init.js which at module load fetches a platform-specific binary from hostnames reassembled at runtime from split string arrays (oob-worker.cf10-1-adf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev), with a fallback that reconstructs a base64 payload from numbered DNS TXT records under c.<domain>/<n>.<domain> resolving under *.dl.wel1.ru. The retrieved bytes are written to /var/tmp/.cache<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows (filename mimicking.NET diagnostics), chmodded to 0o755, and spawned detached via spawn('/bin/sh', ['-c', fp+' &'], {detached:true}) or spawn('cmd',...). Destination hosts are anonymous workers.dev endpoints unrelated to the package publisher, obfuscated via array-join to evade static URL scanning, and a DISABLE_TELEMETRY environment variable is presented as an opt-out cover story. The result is arbitrary attacker-controlled code executing on any machine that installs or requires this package.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-legacy-telephony-panel (version 35.5.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-legacy-telephony-panel across your stack and pipelines.
If you installed it — respond
bigops-legacy-telephony-panel is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If bigops-legacy-telephony-panel 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-legacy-telephony-panel 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-legacy-telephony-panel-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.