GHSA-5cmc-vx46-22wx: Malicious code in dowload_ebok_nur_mal_schnell_das_mammut_retten_by_knut_kruger_eva_schoffmann_davidov_ouz6t (npm)
--- -= Per source details. Do not edit below this line.=-
Source: amazon-inspector (097a05ce21d55f308b754a0dfea3bc1d16b0096187cb6201926527754781fd56) Package contains two files with no a static rule matches and no traced installer-harming behavior. No lifecycle scripts, no network activity, no credential or filesystem access, and no obfuscated or fetched code paths were observed. The package name resembles placeholder or test content rather than a functional library, and the version string (0.0.0-stage) is consistent with a staging or pre-release artifact.
Source: ghsa-malware (e3186ecbf422a5269d156a1c028f6b2507d2a6c4c81edb8b4bc0a3ba61bdb8f8) 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/dowload_ebok_nur_mal_schnell_das_mammut_retten_by_knut_kruger_eva_schoffmann_davidov_ouz6tfrom your environment.Remove the package from any computer where it is installed or running; 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
What should teams do if this package is present on a system?
Treat any computer where the package was installed or run as fully compromised. Remove the package, rotate all secrets and keys from a different computer, and account for the possibility that removal alone may not eliminate malicious software.
Does the available analysis identify a specific malicious installation behavior or indicator to hunt for?
No. The provided source analysis observed no lifecycle scripts, network activity, credential or filesystem access, obfuscated code, fetched code paths, static-rule matches, or traced installer-harming behavior. This absence does not override the guidance to treat an installed or running instance as a full compromise.