GHSA-9fhg-r3w6-g7r4: Malicious code in @k18k/entrypoint-sdk-linux-x64 (npm)
--- -= Per source details. Do not edit below this line.=-
Source: amazon-inspector (daa27c796b86115cf9b0b7113f614ec7e53edb15e4b03b2ec52c10b4a2fb23a2) Package @k18k/entrypoint-sdk-linux-x64@0.2.1 is a linux-x64 platform-specific companion artifact, consistent with the common npm pattern of distributing prebuilt native binaries as separate optionalDependencies per OS/arch. No lifecycle scripts, no install-time network fetches, no credential reads, no exfiltration code paths, and no obfuscated loaders were observed in the three scanned files. No installer-harm signals are present.
Source: ghsa-malware (01bb254d0d26a850aea04e15a4b52039c1ba200ae62a293370e8e10799d683c2) 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
@k18k/entrypoint-sdk-linux-x64from your environment.Remove the package @k18k/entrypoint-sdk-linux-x64.
- Operational
Rotate all secrets and keys stored on any computer that has this package installed or running, immediately and from a different computer.
Event History
Frequently Asked Questions
Which systems should be treated as exposed?
Any computer where this package is installed or running should be considered fully compromised, according to the advisory. The package is a Linux x64 platform-specific artifact, so exposure is relevant to environments that install that variant.
What should be done immediately after identifying an installation?
Rotate all secrets and keys stored on the affected computer immediately, using a different computer. Remove the package, but do not assume removal eliminates any malicious software or unauthorized control resulting from its installation.
Does the available package inspection identify a malicious installation mechanism?
The cited Amazon Inspector scan of version 0.2.1 found no lifecycle scripts, install-time network fetches, credential reads, exfiltration paths, obfuscated loaders, or installer-harm signals in the three scanned files. This does not override the advisory guidance to treat systems with the package installed or running as fully compromised.