Malware in backoffice-charges-module
Malware discovered in the npm package backoffice-charges-module. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- backoffice-charges-module
The npm package backoffice-charges-module has been identified as containing malware. According to the GitHub advisory, 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. The malicious package should be removed, though complete removal of all malicious artifacts cannot be guaranteed due to the potential for full system compromise.\n\nThis is a critical supply chain incident affecting the npm ecosystem, with the potential to compromise any development or production environment where the package was deployed.
Indicators of compromise
- Packages
- backoffice-charges-module
Remediation
- Immediately isolate any system with backoffice-charges-module installed from the network
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the backoffice-charges-module package from all systems
- Conduct a full security audit and malware scan of affected systems
- Review all access logs and activity on compromised systems for signs of unauthorized access
- Consider the affected systems as potentially fully compromised and plan for complete rebuild if critical infrastructure
Sources
- GitHub Advisory GHSA-mmhq-hrgp-xjhx · GitHub Advisory Database
Cite this entry
"Malware in backoffice-charges-module." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 23, 2026; last updated June 23, 2026. https://supplychainattack.org/incident/malware-in-backoffice-charges-module-1bhvcv
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- activecritical
Malware in vitest-cli
Malware discovered in the npm package vitest-cli. Systems with this package installed or running should be considered fully compromised. All secrets and keys must be rotated from a different computer.
npmCompromised package - containedcritical
Malware in ts-sudo
The npm package ts-sudo was found to contain malware, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package - activecritical
Malware in ts-numbering
Malware discovered in the npm package ts-numbering. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - activecritical
Malware in libsignal-node-travatiger
Malware discovered in the npm package libsignal-node-travatiger. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package