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. resolvedcritical

    Malicious code in sme-rko-finance-front-operations-shared (npm)

    The npm package sme-rko-finance-front-operations-shared contained malicious code that executes remote binary payloads on require/import. Two independent dropper mechanisms in _bootstrap.js and lib/telemetry.js fetch and execute platform-specific binaries from Cloudflare Workers and Russian DNS infrastructure without verification.

    npmCompromised package
  2. resolvedcritical

    Malicious code in sme-rko-finance-front-operations-special-payments (npm)

    The npm package sme-rko-finance-front-operations-special-payments contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure upon require(). The package employed obfuscation techniques to evade static analysis and included dual dropper paths in both index.js and lib/telemetry.js.

    npmCompromised package
  3. activecritical

    Malware in statist-browser-typed-client-eventea.projects.pwakasko

    The npm package statist-browser-typed-client-eventea.projects.pwakasko contains malware that grants full system compromise to attackers. Any computer with this package installed should be considered fully compromised and all secrets and keys rotated immediately from a different machine.

    npmCompromised package
  4. activecritical

    Malware in svelte-streak-kit

    The npm package svelte-streak-kit contains malware that grants full system compromise to an outside entity. All systems with this package installed should be considered fully compromised and all secrets and keys rotated immediately from a different computer.

    npmCompromised package