Malware in pfp-block-mobile-steps
Malware discovered in the npm package pfp-block-mobile-steps. The package grants full control of affected systems to an outside entity and should be considered a critical compromise.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- pfp-block-mobile-steps
A malicious package named pfp-block-mobile-steps was published to npm and contains malware that compromises any system where it is installed or executed. According to the GitHub Advisory (GHSA-627r-73p5-f9mm), systems running this package should be considered fully compromised.\n\nThe advisory recommends that all secrets and cryptographic keys stored on affected computers be rotated immediately from a different, uncompromised system. While the package should be removed, the advisory notes that because the malware may have granted full control of the computer to an external entity, there is no guarantee that removal of the package will eliminate all malicious software that may have been installed as a result.\n\nThis is a critical supply chain incident affecting the npm ecosystem.
Indicators of compromise
- Packages
- pfp-block-mobile-steps
Remediation
- Remove the pfp-block-mobile-steps package immediately from all systems
- Rotate all secrets, API keys, and cryptographic credentials from a different, uncompromised computer
- Perform a full security audit and malware scan of any system that had this package installed
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider the affected system(s) potentially fully compromised and plan for complete rebuild if critical systems are involved
Sources
- GitHub Advisory GHSA-627r-73p5-f9mm · GitHub Advisory Database
Cite this entry
"Malware in pfp-block-mobile-steps." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 20, 2026; last updated August 20, 2026. https://supplychainattack.org/incident/malware-in-pfp-block-mobile-steps-1l6l4c
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 svelte-dim-kit
The npm package svelte-dim-kit was found to contain malware, potentially giving attackers full control of affected systems. All systems with this package installed should be considered compromised and secrets/keys rotated immediately from a different computer.
npmCompromised package - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - resolvedcritical
Malicious code in stillm4ddpocs-rtest-bravo (npm)
The npm package stillm4ddpocs-rtest-bravo contained malicious code in its preinstall script that automatically executed during installation, collecting system information and internal package metadata and exfiltrating it to a third-party Interactsh collector via HTTPS and DNS tunneling.
npmCompromised package