Malware in dlp-dlp-core
Malware was discovered in the npm package dlp-dlp-core, resulting in full system compromise for any installation. All affected systems should be considered fully compromised and all secrets and keys rotated from a clean machine.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- dlp-dlp-core
A critical malware incident was identified in the npm package dlp-dlp-core. According to the GitHub Security Advisory (GHSA-grjf-cv97-2hjr), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated immediately from a different, uncompromised machine. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise, given that the attacker may have gained full control of the system.\n\nThe affected package is dlp-dlp-core on npm. Organizations should audit their dependencies and systems for any installations of this package and take immediate remediation steps.
Indicators of compromise
- Packages
- dlp-dlp-core
Remediation
- Identify all systems with dlp-dlp-core installed or running
- Isolate affected systems from the network immediately
- Rotate all secrets, API keys, and credentials from a clean, uncompromised machine
- Remove the dlp-dlp-core package from all affected systems
- Conduct a full forensic investigation to identify any additional malicious software or persistence mechanisms
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Restore systems from clean backups if available, or rebuild from scratch
- Implement additional monitoring and detection rules for similar malicious packages
Sources
- GitHub Advisory GHSA-grjf-cv97-2hjr · GitHub Advisory Database
Cite this entry
"Malware in dlp-dlp-core." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malware-in-dlp-dlp-core-125oim
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 @ai-vertical/ai-agent
Malware was discovered in the npm package @ai-vertical/ai-agent. Systems with this package installed or running should be considered fully compromised and require immediate remediation.
npmAI agents & skillsCompromised package - resolvedcritical
Malicious code in epic-sso (npm)
The npm package epic-sso was found to contain malicious code. The package was identified by Amazon Inspector and reported through the OpenSSF malicious packages database.
npmCompromised package - resolvedcritical
Malicious code in epic-common-node (npm)
The npm package epic-common-node was found to contain malicious code. The package has been identified and reported through GitHub Security Advisory GHSA-m36g-mhjr-ww2c.
npmCompromised package - containedcritical
Malicious code in checkout-desktop-total (npm)
The npm package checkout-desktop-total contained malicious code that executes a hidden loader on import, downloading and running platform-specific native payloads from attacker-controlled Cloudflare Workers hosts or reconstructing them via DNS TXT records under wel1.ru. Any system that imported this package should be considered compromised.
npmCompromised package