Malware in pfp-integration-mobile-heading
Malware discovered in the npm package pfp-integration-mobile-heading. 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
- pfp-integration-mobile-heading
A malicious package named pfp-integration-mobile-heading was published to npm and contains malware. Any computer with this package installed or running should be considered fully compromised.\n\nThe malware grants outside entities full control of affected systems. All secrets and keys stored on compromised computers should be rotated immediately from a different, unaffected system.\n\nWhile the package should be removed, complete removal of all malicious software cannot be guaranteed due to the level of system compromise. A full security audit and potential system rebuild may be necessary for affected users.
Indicators of compromise
- Packages
- pfp-integration-mobile-heading
Remediation
- Immediately remove the pfp-integration-mobile-heading package from all systems
- Rotate all secrets, API keys, and credentials from a different, unaffected computer
- Conduct a full security audit of any system that had this package installed
- Consider rebuilding affected systems from clean media if full compromise is suspected
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Monitor for any unauthorized activity on accounts or services that may have been accessed from compromised systems
Sources
- GitHub Advisory GHSA-w5mx-8jxc-vmcw · GitHub Advisory Database
Cite this entry
"Malware in pfp-integration-mobile-heading." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malware-in-pfp-integration-mobile-heading-1t8qih
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