Which versions of bigops-telephony are malicious?

The following npm versions of bigops-telephony are flagged malicious: 35.8.4. Treat any of these as compromised.

How do I remediate bigops-telephony if I installed it?

bigops-telephony 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.

I already installed bigops-telephony — how do I know if it already compromised me?

If bigops-telephony 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.

Is bigops-telephony part of a known attack campaign?

Yes — bigops-telephony is associated with the IN-MAL-2026-015545, GHSA-j5w7-ccfc-4mrf campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find bigops-telephony across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-telephony (version 35.8.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-telephony across your stack and pipelines.

Malicious package

bigops-telephonynpm

bigops-telephony is a confirmed malicious npm package (MAL-2026-12840) that steals credentials and exfiltrates sensitive data (malicious version 35.8.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bigops-telephony (npm)

MAL-2026-12840

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall bigops-telephony

What this malware does

On require('bigops-telephony'), index.js loads adapter.js which selects a platform-specific asset path, fetches an opaque binary from one of three runtime-assembled workers.dev hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev) with a DNS-TXT base64-reassembly fallback under *.dl.wel1.ru, writes it to /var/tmp or %TEMP% under disguised names such as dotnet_diag<rand>.exe or.cache_<rand>, chmods 0755, and spawns it detached via /bin/sh -c or cmd.exe. Host strings are reassembled from split arrays at runtime and execution is gated by environment variables (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) plus a marker file at /tmp/.analytics_state to mimic legitimate telemetry. A second, currently-unreferenced dropper module at lib/telemetry.js is shipped alongside and performs the same base64-decode -> chmod 755 -> spawn /bin/sh chain under an 'analytics SDK' cover story.

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

1 flagged

35.8.4

Indicators of compromise (SHA-256)

da1b7311c033191d85d0d19c679ac9d453f7517897b57618d0d8977d654daf94

6a9e2c06ce50f9e0d2275d948ef9c802f9c234f8283c30416a745d3db3d1b46d

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-telephony (version 35.8.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-telephony across your stack and pipelines.
If you installed it — respond
bigops-telephony 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-telephony 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-telephony 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

No. bigops-telephony on npm has been identified as a malicious package (version 35.8.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015545GHSA-j5w7-ccfc-4mrf

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-telephony-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database