Malware in calculate-helper
Malware discovered in the npm package calculate-helper. The package grants full system compromise to attackers and should be considered a critical threat to any system where it is installed or running.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- calculate-helper
The npm package calculate-helper has been identified as containing malware. According to the GitHub Advisory (GHSA-3cmh-x7h7-f97c), 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 package should be removed, though complete remediation cannot be guaranteed due to the potential for the malware to have established persistent access or additional backdoors on the system.\n\nThis is a critical supply chain incident affecting the npm ecosystem, with the potential to compromise any developer or system that has installed or executed this package.
Indicators of compromise
- Packages
- calculate-helper
Remediation
- Immediately remove the calculate-helper package from all systems
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Audit system logs for unauthorized access or activity
- Consider the affected system fully compromised and plan for complete rebuild if critical infrastructure
- Monitor for any persistence mechanisms or additional malware that may have been installed
Sources
- GitHub Advisory GHSA-3cmh-x7h7-f97c · GitHub Advisory Database
Cite this entry
"Malware in calculate-helper." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 23, 2026; last updated June 23, 2026. https://supplychainattack.org/incident/malware-in-calculate-helper-hji7s3
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