Malware in pure-folder-three
The npm package pure-folder-three was found to contain malware. Installation of the package results in full system compromise, requiring immediate removal and credential rotation from a clean system.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed
- Ecosystems
- Attack vectors
- Affected entities
- pure-folder-threenpm package
The npm package pure-folder-three was identified as containing malware. According to the GitHub Advisory (GHSA-9w58-3cgj-jw7v), any computer with this package installed or running should be considered fully compromised.
The advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning removal of the package alone may not eliminate all malicious software that resulted from installation.
The package was published on npm and flagged as critical severity by GitHub's security advisory system.
Indicators of compromise
- Packages
- pure-folder-three
Remediation
- Immediately isolate any computer with pure-folder-three installed from the network
- Rotate all secrets, API keys, and credentials from a clean, uncompromised system
- Remove the pure-folder-three package from all affected systems
- Perform a full security audit and malware scan of affected systems
- Review system logs and access patterns for signs of unauthorized activity
- Consider full system reimaging if the system contained highly sensitive data or credentials
Sources
- GitHub Advisory GHSA-9w58-3cgj-jw7v · GitHub Advisory Database
Cite this entry
"Malware in pure-folder-three." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 13, 2026; last updated July 13, 2026. https://supplychainattack.org/incident/malware-in-pure-folder-three-16jdym
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- activecritical
Malware in dotnet-runtime-base
Malware discovered in the npm package dotnet-runtime-base. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - resolvedcritical
Malware in node-sysmetrics
Malware was discovered in the npm package node-sysmetrics, providing full system compromise to any computer with the package installed or running. All affected systems should be considered fully compromised and all secrets and keys rotated from a different computer.
npmCompromised package - activecritical
Malware in authvaultx
Malware discovered in the npm package authvaultx. Systems with this package installed or running are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
jscrambler npm package publishes malicious preinstall binary
Version 8.14.0 of the jscrambler npm package, the official CLI client for Jscrambler Code Integrity API, was published on July 11, 2026 with a malicious preinstall hook that drops and executes platform-specific native binaries on Linux, Windows, and macOS. The compromise was detected by StepSecurity's AI Release Analyzer immediately upon publication.
npmCompromised package