Which versions of gke-net are malicious?

The following npm versions of gke-net are flagged malicious: 9.9.9. Treat any of these as compromised.

How do I remediate gke-net if I installed it?

Remove gke-net from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed gke-net — how do I know if it already compromised me?

If gke-net was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is gke-net part of a known attack campaign?

Yes — gke-net is associated with the RLMA-2026-01955 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find gke-net across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for gke-net (version 9.9.9).

Malicious package

gke-netnpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

gke-net is a confirmed malicious npm package (MAL-2026-2766) that executes malicious code on install (malicious version 9.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gke-net (npm)

MAL-2026-2766

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall gke-net

What this malware does

The package gke-net was found to contain malicious code.

Malicious versions

1 flagged

9.9.9

Indicators of compromise (SHA-256)

5aa40d2376d9aa99dae6f434c3f723db293b92cb8d00523ea509b4a8c6b71e1e

74d8166ccce1b949aaac0d7138ed8faf7494ac88239e6ff2f00cfdb1d1be4011

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for gke-net (version 9.9.9).
If you installed it — respond
Remove gke-net from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If gke-net was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. gke-net on npm has been identified as a malicious package (version 9.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01955

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks gke-net-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database