Malware in karem-dp
The npm package karem-dp was found to contain malware. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- karem-dpnpm package containing malware
The npm package karem-dp has been identified as containing malware. According to the GitHub advisory (GHSA-qfm3-6pmh-jr8j), any computer that has this package installed or running should be considered fully compromised.\n\nImmediate action is required: all secrets and keys stored on affected computers should be rotated immediately from a different, uncompromised computer. 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 package installation, as the attacker may have gained full control of the system.\n\nThis is a critical supply chain incident affecting the npm ecosystem.
Indicators of compromise
- Packages
- karem-dp
Remediation
- Immediately rotate all secrets and keys from a different, uncompromised computer
- Remove the karem-dp package from all affected systems
- Audit system logs for unauthorized access or modifications
- Consider the affected computer(s) as potentially fully compromised and plan for forensic analysis or complete system rebuild
- Check for any other suspicious packages or modifications on affected systems
- Notify all users and systems that may have used this package
Sources
- GitHub Advisory GHSA-qfm3-6pmh-jr8j · GitHub Advisory Database
Cite this entry
"Malware in karem-dp." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 8, 2026; last updated July 8, 2026. https://supplychainattack.org/incident/malware-in-karem-dp-cyvauf
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in test2221 (npm)
The npm package test2221 version 2.2.4 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - containedcritical
Malware in n8n-nodes-trust-me-im-totally-safe
Malware was discovered in the npm package n8n-nodes-trust-me-im-totally-safe, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package - activecritical
Malware in litespeed-cache
Malware discovered in the npm package litespeed-cache. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
npmCompromised package - containedcritical
Malware in open-worker-cli
Malware was discovered in the npm package open-worker-cli. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
npmCompromised package