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
- containedcritical
Malware in fetch-runtime
Malware was discovered in the npm package fetch-runtime. Any system with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package - resolvedcritical
Malicious code in ghazaly (npm)
The npm package ghazaly version 99.9.0 contained malicious code that executed a postinstall hook to collect system information (hostname, current user, IP addresses) and exfiltrate it to a Burp Collaborator domain. The package exhibited dependency-confusion characteristics with a high version number and nonsense dependencies.
npmCompromised packageDependency confusion - containedcritical
Malicious code in base65-13x (npm)
base65-13x@5.0.2 on npm contains malicious obfuscated code disguised as a legitimate base-x library. The decode() function executes a ~123KB VM-style payload with dynamic code construction and network I/O capabilities.
npmCompromised package - containedcritical
Malicious code in kit-vim-map (npm)
The npm package kit-vim-map contained malicious code that executes a remote-controlled Linux ELF binary on installation, providing the attacker with arbitrary RCE, persistence, and file exfiltration capabilities. The binary beacons to C2 server 217.60.77.63 and establishes persistence via systemd user units.
npmCompromised packageMalicious commit