MAL-2026-10402 Malicious code in @gleamkit/ws (npm)
Malicious package
Published
MAL-2026-10402 is a malicious package: @gleamkit/ws (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-10402/ (Markdown: https://insights.sbomify.com/MAL-2026-10402/index.md)
- Package
- @gleamkit/ws
- Registry
- npm
What is MAL-2026-10402?
MAL-2026-10402 is a malicious package in @gleamkit/ws, published on 13 Jul 2026.
Official description
The package publishes under scope
@gleamkit/ws while copying the ws package's description, homepage, repository, author, and README verbatim, and bundling the legitimate ws source so it appears functional. Appended to lib/websocket.js after the copied WebSocket implementation is a heavily obfuscated payload (base64+RC4 string decoder over a ~700-entry rotated string array, hex-named identifiers, duplicated as two sequential IIFEs) that reconstructs hostnames, paths, environment keys, and spawn arguments at runtime. On every load — index.js (main) and wrapper.mjs both pull in ./lib/websocket — the payload issues an HTTPS request to fetch an external binary, AES-256-GCM decrypts it, writes it under os.tmpdir(), chmods it to 0o755, and spawns it as a detached, unref()ed child process with windowsHide:true, then calls process.exit. A marker env variable gate (process.env[d]!== e) is used to avoid re-entry. Because require/import is the trigger, any project that installs and loads @gleamkit/ws executes attacker-controlled bytes fetched from a remote host at load time.What should I do about MAL-2026-10402?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.