MAL-2026-18397: Malicious code in dowload_ebok_armageddon_by_max_hastings_kv3s4 (npm)
--- -= Per source details. Do not edit below this line.=-
Source: amazon-inspector (69968aae3c0971eb7e0aae79515930942260191d6a07871fd8fb6f863744b372) Package dowloadebokarmageddonbymaxhastingskv3s4 version 0.0.0-stage ships minimal content with no executable code, no lifecycle scripts, no network activity, and no filesystem access. The package name resembles ebook-piracy spam rather than a functional software package, but the shipped contents perform no action against the installer.
Source: ghsa-malware (873b28eebd2c4a6110621c41dd8d5945f3f7aa716e9110d17b62afa80a2958ff) 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_armageddon_by_max_hastings_kv3s4from your environment.Remove the package dowload_ebok_armageddon_by_max_hastings_kv3s4.
- Operational
Rotate all secrets and keys stored on the affected computer immediately, using a different computer.
Event History
Frequently Asked Questions
Which package version is identified in the available source details?
The Amazon Inspector source details identify version 0.0.0-stage.
What systems should be treated as exposed?
The GHSA malware source says that any computer with the package installed or running should be considered fully compromised. It recommends rotating all secrets and keys stored on that computer from a different computer.
Is removing the package sufficient remediation?
No. The GHSA malware source recommends removing the package but warns that removal may not eliminate all malicious software because an outside entity may have obtained full control of the computer.
Did the inspected package contents perform actions during installation?
The Amazon Inspector source reports that the inspected package content had no executable code, lifecycle scripts, network activity, or filesystem access. This differs from the GHSA malware source's compromise assessment, so remediation should account for that assessment rather than relying only on package removal.