Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in bigops-videocalls

Malware was discovered in the npm package bigops-videocalls, resulting in full system compromise for any installation. The package should be removed and all secrets and keys rotated from a different computer.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • bigops-videocalls

The npm package bigops-videocalls was found to contain malware. According to the GitHub Advisory (GHSA-mg7c-j5rh-f6g9), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated from a different, uncompromised system. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise, given that the attacker may have gained full control of the system.\n\nUsers should assume complete system compromise and take appropriate defensive measures accordingly.

Indicators of compromise

Packages
  • bigops-videocalls

Remediation

  • Remove the bigops-videocalls package immediately
  • Rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Assume full system compromise and consider rebuilding affected systems from clean media
  • Audit system logs for unauthorized access or modifications
  • Monitor for any lateral movement or persistence mechanisms installed by the malware

Sources

  1. GitHub Advisory GHSA-mg7c-j5rh-f6g9 · GitHub Advisory Database

Cite this entry

"Malware in bigops-videocalls." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malware-in-bigops-videocalls-6alnla

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. containedcritical

    Malware in svelte-dim-kit

    The npm package svelte-dim-kit was found to contain malware, potentially giving attackers full control of affected systems. All systems with this package installed should be considered compromised and secrets/keys rotated immediately from a different computer.

    npmCompromised package
  2. containedcritical

    Malicious code in @syncraft-labs/react (npm)

    The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.

    npmCompromised package
  3. containedcritical

    Malicious code in stillm4ddpocs-demo-sprocket (npm)

    The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.

    npmCompromised packageDependency confusion
  4. resolvedcritical

    Malicious code in stillm4ddpocs-rtest-bravo (npm)

    The npm package stillm4ddpocs-rtest-bravo contained malicious code in its preinstall script that automatically executed during installation, collecting system information and internal package metadata and exfiltrating it to a third-party Interactsh collector via HTTPS and DNS tunneling.

    npmCompromised package