Malware in bigops-chat-messages
Malware was discovered in the npm package bigops-chat-messages. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- bigops-chat-messages
The npm package bigops-chat-messages was found to contain malware. According to the GitHub Advisory (GHSA-7fcf-754p-pfhv), any computer with this package installed or running should be considered fully compromised.\n\nImmediate action is required: all secrets and keys stored on affected computers must be rotated immediately 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 package installation, given that the outside entity may have gained full control of the system.\n\nAffected users should assume complete system compromise and take appropriate incident response measures.
Indicators of compromise
- Packages
- bigops-chat-messages
Remediation
- Immediately rotate all secrets and keys from a different, uncompromised computer
- Remove the bigops-chat-messages package from all affected systems
- Conduct a full security audit and forensic analysis of any system that had this package installed
- Monitor affected systems for signs of persistent malware or unauthorized access
- Consider rebuilding affected systems from clean media if full compromise is suspected
Sources
- GitHub Advisory GHSA-7fcf-754p-pfhv · GitHub Advisory Database
Cite this entry
"Malware in bigops-chat-messages." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 3, 2026; last updated August 3, 2026. https://supplychainattack.org/incident/malware-in-bigops-chat-messages-k80bcz
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in @types-beta/sdk (npm)
The npm package @types-beta/sdk (versions 0.1.0–0.1.3) is a supply-chain dropper that impersonates the trusted @types/DefinitelyTyped namespace. It bundles a Windows executable (nanocache.exe) that executes at import time, establishing a persistent remote-access agent with command-and-control capabilities.
npmCompromised packageTyposquatting - containedcritical
Malware in fluid-type-ui
Malware was discovered in the npm package fluid-type-ui. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
npmCompromised package - containedcritical
Malware in accounts-loading-state
The npm package accounts-loading-state was found to contain malware, potentially giving full control of affected systems to an outside entity. All systems with this package installed should be considered fully compromised.
npmCompromised package - activecritical
Malware in internallib_v524
Malware discovered in the npm package internallib_v524. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package