Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
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
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for gemini-cli-a2a-server (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gemini-cli-a2a-server across your stack and pipelines.

  2. 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.

  3. Did it already run?

    If gemini-cli-a2a-server was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks gemini-cli-a2a-server before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

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

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.

Explore