Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

gemini-ai-apiPyPI

Malicious code in gemini-ai-api (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-2268
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall gemini-ai-api

What this malware does

Clones of legitimate libraries with malicious modifications intended to download malicious remote code. The remote script allows executing arbitrary files through a Telegram as C2 channel. The package installs a generic entry point triggering malicious action.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-03-pipipipi

Reasons (based on the campaign):

  • clones-real-package

  • rat

  • Downloads and executes a remote malicious script.

  • typosquatting

Malicious versions

1 flagged
2.33.0

Indicators of compromise (SHA-256)

eaf9c608a9f21071f08ed32d460d46e974fc20d40aa3ecd3415c533a09165748
db2be37ea455b54b825242a3f66310fdf3f70e50b1dc1a234fa3ebb534afa857

Detection & response playbook

Credential / info stealer
  1. Find it

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

  2. If you installed it — respond

    gemini-ai-api is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If gemini-ai-api 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-ai-api 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-ai-api on PyPI has been identified as a malicious package (version 2.33.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-03-pipipipi

References

Credits

  • Kamil Mańkowski (kam193) · analyst

Detect & block this

O3 blocks gemini-ai-api-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

gemini-ai-api (PyPI) malicious package — MAL-2026-2268 | O3 Security