Which versions of bigops-telephony-mock are malicious?

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

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

bigops-telephony-mock 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-mock — how do I know if it already compromised me?

If bigops-telephony-mock 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-mock part of a known attack campaign?

Yes — bigops-telephony-mock is associated with the IN-MAL-2026-016878 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-mock 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-mock (version 35.7.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-telephony-mock across your stack and pipelines.

Malicious package

bigops-telephony-mocknpm

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

Malicious code in bigops-telephony-mock (npm)

MAL-2026-13494

Immediate action

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

npm uninstall bigops-telephony-mock

What this malware does

Requiring the package (index.js ->./setup) triggers setup.js, which reconstructs destination hostnames from split string fragments (e.g. oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS-TXT fallback across sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru, downloads a platform-specific binary via https.get, writes it to a disguised path under /tmp or %TEMP% (names such as analytics_state, dotnet_diag_.exe,.cache_), fs.chmodSync's it to 0755, and cp.spawn's it detached via /bin/sh -c '<file> &' or cmd.exe /c start /b. No version pin, no hash or signature verification, and destinations are assembled at runtime to defeat static inspection; child_process itself is required as "child_" + "process" in lib/telemetry.js. A second copy of the same download->base64-decode->chmod 755->spawn /bin/sh loader is bundled under lib/telemetry.js (approximately 81KB) framed as a telemetry SDK. The behavior fires on any require()/import of the package, gated only by an opt-out env var and a TTL marker file, so a normal npm install followed by loading the module causes attacker-controlled code to execute on the installer's machine.

Malicious versions

1 flagged

35.7.2

Indicators of compromise (SHA-256)

ccbd56ae20f9cc922c12df25456654a649c9bbc963aae4fa95e027f97628c45b

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-mock (version 35.7.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-telephony-mock across your stack and pipelines.
If you installed it — respond
bigops-telephony-mock 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-mock 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-mock 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-mock on npm has been identified as a malicious package (version 35.7.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016878

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-telephony-mock-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