Which versions of gemini-cli-a2a-server are malicious?

The following npm versions of gemini-cli-a2a-server are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate gemini-cli-a2a-server if I installed it?

gemini-cli-a2a-server is a typosquat — you almost certainly intended a legitimately-named package. Remove gemini-cli-a2a-server, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed gemini-cli-a2a-server — how do I know if it already compromised me?

If gemini-cli-a2a-server 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 gemini-cli-a2a-server part of a known attack campaign?

Yes — gemini-cli-a2a-server is associated with the IN-MAL-2026-018341 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 gemini-cli-a2a-server across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for gemini-cli-a2a-server (version 1.0.0).

Malicious package

gemini-cli-a2a-servernpm

gemini-cli-a2a-server is a confirmed malicious npm package (MAL-2026-14244) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gemini-cli-a2a-server (npm)

MAL-2026-14244

Immediate action

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

npm uninstall gemini-cli-a2a-server

What this malware does

On npm install, the package's postinstall script collects host identifiers (os.hostname(), platform, arch, Node version, and package/lifecycle metadata) and POSTs them via https.request to the hardcoded endpoint https://onpx9s3x.instances.poc.jchunt.top/gemini-cli-a2a-server. The package name mimics a private Google Gemini CLI a2a-server component, and a source.txt reference in the tarball points at that internal package — consistent with a dependency-confusion probe that pings out from any environment that inadvertently resolves this public name instead of the intended private one.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

5eb13d8d28e4c8363ceabe294b988cd42a82f1875af3f2a30310232154664afd

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for gemini-cli-a2a-server (version 1.0.0).
If you installed it — respond
gemini-cli-a2a-server is a typosquat — you almost certainly intended a legitimately-named package. Remove gemini-cli-a2a-server, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If gemini-cli-a2a-server 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. gemini-cli-a2a-server on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018341

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks gemini-cli-a2a-server-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