Which versions of bigops-voximplant are malicious?

The following npm versions of bigops-voximplant are flagged malicious: 20.8.5, 35.4.8. Treat any of these as compromised.

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

Remove bigops-voximplant 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.

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

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

Yes — bigops-voximplant is associated with the IN-MAL-2026-014418, IN-MAL-2026-015519, GHSA-r63g-878r-qfjf 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-voximplant 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-voximplant (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-voximplant across your stack and pipelines.

Malicious package

bigops-voximplantnpm

bigops-voximplant is a confirmed malicious npm package (MAL-2026-12172) that executes malicious code on install (malicious versions 20.8.5, 35.4.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bigops-voximplant (npm)

MAL-2026-12172

Immediate action

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

npm uninstall bigops-voximplant

What this malware does

On require() of bigops-voximplant, index.js loads ext.js which downloads an OS/arch-specific binary from Cloudflare Workers subdomains whose hostnames are reassembled at runtime from split string fragments (oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev), with a DNS-over-TXT base64 chunked fallback resolving from sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru to bypass HTTPS egress filtering. The fetched bytes are written to /tmp/.cache<hex> on Unix (or %TEMP%\dotnet_diag_<hex>.exe on Windows), chmod'd 0755 via fs['chmod'+'Sync'], and detached-spawned via /bin/sh -c '<path> &' or cmd /c start /b, with no hash or signature verification and no source-of-truth publisher domain. A second, structurally identical dropper is bundled as lib/telemetry.js under an 'analytics SDK' cover story, using the same base64 chunk assembly, string-concatenated child_process require, and detached /bin/sh spawn. Hosts and dangerous APIs are constructed via runtime string joins ('child_'+'process', split-and-join hostname fragments) to defeat static inspection. The destinations are anonymous Cloudflare Workers and a.ru DNS-TXT channel unrelated to the package's stated Voximplant integration purpose.

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

2 flagged

20.8.535.4.8

Indicators of compromise (SHA-256)

c67a56841b4588b155f5b2470d87c8d36c476b1a6eddf3f8a75e8fe5d49c9624

e20e151930946a17e9bea02eb51c760264c27138792955452acc4231196ceaae

883fad29cd53f12c99b7191ee77a0400cca0ee0911467b88f5d64f8b3402798a

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bigops-voximplant (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-voximplant across your stack and pipelines.
If you installed it — respond
Remove bigops-voximplant 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-voximplant 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-voximplant 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-voximplant on npm has been identified as a malicious package (versions 20.8.5, 35.4.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014418IN-MAL-2026-015519GHSA-r63g-878r-qfjf

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-voximplant-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database