MalwarePublished 23 Oct 2026Updated 29 Oct 2026

@k18k/entrypoint-sdk-linux-x64 (npm) · Malicious Code

Affects @k18k/entrypoint-sdk-linux-x64Source GCVE Database

Malicious package : remove @k18k/entrypoint-sdk-linux-x64 and rotate any secrets on hosts that installed it.

Data as of 29 Oct 2026, 18:35 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-18245

What to do

Remove @k18k/entrypoint-sdk-linux-x64 from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npm@k18k/entrypoint-sdk-linux-x64	Affected =0.2.0 =0.2.1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The npm package @k18k/entrypoint-sdk-linux-x64 versions 0.2.0 and 0.2.1 contain malicious code. Installation or execution of this package can lead to full system compromise. Users should consider any system with this package installed as fully compromised and rotate all secrets and keys from a different machine. Removal of the package does not guarantee removal of all malicious software introduced.

Impact

Systems with the package installed or running are considered fully compromised, risking exposure of all stored secrets and keys. The attacker may have gained full control over the affected computer, leading to potential data theft, unauthorized access, and persistent malicious presence.

Defensive guidance

Immediately remove the @k18k/entrypoint-sdk-linux-x64 package from affected systems. Rotate all secrets and keys stored on the compromised machine from a separate, secure computer. Due to the potential for persistent compromise, consider full system reimaging or forensic analysis to ensure removal of all malicious components.

Summary

The package @k18k/entrypoint-sdk-linux-x64, specifically versions 0.2.0 and 0.2.1, is identified as malicious. Despite no observed installer-harm signals such as lifecycle scripts, network fetches during install, credential reads, or obfuscated loaders, the package is considered fully compromising to any system where it is installed or running. The compromise is severe enough that all secrets and keys on the affected system should be rotated immediately from a separate, trusted machine. Removal of the package alone is insufficient to ensure system integrity due to potential persistence of malicious software.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2026, 18:35 UTC

Technical details

References

Community reviews