GHSA-h86m-7gvf-j79h: Malicious code in dowload_ebok_reiki_sviluppa_e_usa_lenergia_reiki_by_matt_harvey_9q55p (npm)
--- -= Per source details. Do not edit below this line.=-
Source: amazon-inspector (405e9f78919c848257f022e90ba1326206bee394ec4873cb08b846688258ef15) Package 'dowloadebokreikisviluppaeusalenergiareikibymattharvey9q55p' at version 0.0.0-stage contains only 2 files and shows no code-level behavior of concern: no lifecycle scripts, no network calls, no filesystem or environment access, no credential reads, and no obfuscated or fetched content. The package name and version pattern are consistent with a placeholder or spam/SEO-style registry entry rather than a functioning library.
Source: ghsa-malware (4295f9675d8088438ae91b0dd10004814c4b1f74b4363857d73add0462350820) 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_reiki_sviluppa_e_usa_lenergia_reiki_by_matt_harvey_9q55pfrom your environment.Remove the package dowload_ebok_reiki_sviluppa_e_usa_lenergia_reiki_by_matt_harvey_9q55p.
- Operational
Immediately rotate all secrets and keys stored on any computer with this package installed or running, using a different computer.
Event History
Frequently Asked Questions
Which installations are identified in the available data?
The available data identifies version 0.0.0-stage of the npm package. It states that any computer on which the package is installed or running should be treated as potentially fully compromised.
Is there technical evidence in the package contents explaining the compromise assessment?
One source reports that the package contains only two files and found no lifecycle scripts, network calls, filesystem or environment access, credential reads, obfuscated content, or fetched content. That source characterizes the name and version pattern as consistent with a placeholder or spam/SEO-style registry entry, while the malware advisory nevertheless directs responders to treat affected systems as compromised.
What should responders do if this package is found on a system?
Remove the package, rotate all secrets and keys stored on the affected computer from a different computer, and treat the system as potentially under outside control. Removing the package alone is not guaranteed to remove any malicious software that may have resulted from its installation.