MAL-2026-19215: Malicious code in rampage-unpack (npm)
--- -= Per source details. Do not edit below this line.=-
Source: ghsa-malware (c36796720d574c5c3a1789a90681935e44511af8c17366d2e8499bbb27dca957) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Remove
Remove
npm/rampage-unpackfrom your environment.Remove the rampage-unpack package; removing it may not remove all malicious software resulting from its installation.
- Operational
Rotate all secrets and keys stored on the affected computer immediately, using a different computer.
Event History
Frequently Asked Questions
Who should treat this as an active compromise?
Any computer where the package is installed or running should be considered fully compromised. This includes systems that may have stored secrets or keys accessible to the package.
What should be done immediately?
Rotate all secrets and keys stored on the affected computer, using a different computer to perform the rotation. Remove the package from the affected system.
Is removing the package sufficient to remediate the incident?
No. Because installation may have given an outside entity full control of the computer, removing the package does not guarantee that all malicious software has been removed.