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
- resolvedcritical
Malicious code in autbank-core (npm)
The npm package autbank-core contained malicious preinstall and postinstall lifecycle hooks that exfiltrated environment variables, credentials, and system information to a hardcoded webhook.site endpoint during installation.
npmCompromised package - resolvedcritical
Malicious code in adxaa (npm)
The npm package adxaa contained obfuscated malicious JavaScript designed to target users of a specific WordPress site. The payload exfiltrates session data, deletes accounts, and hijacks credentials via email overwrite and password reset.
npmCompromised package - resolvedcritical
Malicious code in upload-to-gcp (npm)
upload-to-gcp@3.2.1 (npm) contains malicious code in its postinstall script that exfiltrates host identifiers to an attacker-controlled endpoint. The package masquerades as a Google Cloud Platform utility but performs unauthorized telemetry collection at install time.
npmCompromised package - resolvedcritical
Malicious code in akamai-sensor (npm)
A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.
npmCompromised packageTyposquatting