Malware in @reference-web/pmp-i18n
Malware was discovered in the npm package @reference-web/pmp-i18n. 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
- @reference-web/pmp-i18n
A malware incident was identified in the npm package @reference-web/pmp-i18n, published as GitHub Advisory GHSA-m6f5-jgw6-8m97 on June 29, 2026.\n\nAny computer with this package installed or running should be considered fully compromised. The malware grants outside entities full control of affected systems, potentially allowing persistent access beyond package removal.\n\nImmediate remediation requires rotating all secrets and keys from a separate, uncompromised computer, and removing the package. However, complete removal of all malicious artifacts cannot be guaranteed due to the level of system compromise.\n\nUsers should assume that any credentials, API keys, or sensitive data accessible from affected systems have been exposed and require rotation.
Indicators of compromise
- Packages
- @reference-web/pmp-i18n
Remediation
- Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the @reference-web/pmp-i18n package from all affected systems
- Conduct a full security audit of any systems that had this package installed
- Monitor affected systems for signs of persistent malware or unauthorized access
- Consider rebuilding or reimaging severely compromised systems if secrets cannot be fully rotated
Sources
- GitHub Advisory GHSA-m6f5-jgw6-8m97 · GitHub Advisory Database
Cite this entry
"Malware in @reference-web/pmp-i18n." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-reference-web-pmp-i18n-5vsk7q
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