Which versions of bigops-videocalls are malicious?

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

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

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

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

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

Malicious package

bigops-videocallsnpm

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

Malicious code in bigops-videocalls (npm)

MAL-2026-12854

Immediate action

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

npm uninstall bigops-videocalls

What this malware does

On require of the package's main entry, support.js executes at import time: it selects a platform-specific path, fetches an opaque native binary from one of four hardcoded Cloudflare workers.dev hosts (oob-worker.cf101-adf/99-9b3/100-416/103-070.workers.dev), with a DNS TXT covert-channel fallback at *.dl.wel1.ru, writes the bytes to /var/tmp or %TEMP% under disguised filenames (.cache<hex> on POSIX, dotnet_diag_<hex>.exe on Windows), sets mode 0755, and spawns the dropped file detached via /bin/sh -c or cmd.exe /c start. C2 hostnames are assembled from split string arrays (e.g. ['oob-worker.cf101-adf.worker','s.de','v'].join('')) to defeat static IOC extraction, and telemetry opt-out env vars are checked as cover. Dropped filenames impersonate system diagnostics artifacts. Requiring or installing this package results in download-and-execute of attacker-controlled native code on the installer's host.

Malicious versions

1 flagged

35.9.9

Indicators of compromise (SHA-256)

4b04bc16010479f488969366f0af5596c33f668da075e09d5d1b8fad737f03cd

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

Campaign

IN-MAL-2026-015533

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-videocalls-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