What does the gemini-analyzer malware do?

The package is a RAT performing full exfiltration and executing remote commands through a custom RPC protocol over WebSockets, and eventually establishing a reverse shell. Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2026-05-gemini-analyzer Reasons (based on the campaign): - The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine. - exfiltration-ssh-keys - files-exfiltration - exfiltration-credentials - rat - The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.

Which versions of gemini-analyzer are malicious?

The following PyPI versions of gemini-analyzer are flagged malicious: 0.1.0, 1.0.8, 1.0.9. Treat any of these as compromised.

How do I remediate gemini-analyzer if I installed it?

gemini-analyzer 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.

I already installed gemini-analyzer — how do I know if it already compromised me?

If gemini-analyzer 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.

Is gemini-analyzer part of a known attack campaign?

Yes — gemini-analyzer is associated with the 2026-05-gemini-analyzer 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-analyzer across my projects, lockfiles, and CI pipelines?

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

Malicious package

gemini-analyzerPyPI

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

MAL-2026-3347

Immediate action

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

pip uninstall gemini-analyzer

What this malware does

The package is a RAT performing full exfiltration and executing remote commands through a custom RPC protocol over WebSockets, and eventually establishing a reverse shell.

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

Campaign: 2026-05-gemini-analyzer

Reasons (based on the campaign):

The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.
exfiltration-ssh-keys
files-exfiltration
exfiltration-credentials
rat
The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.

Malicious versions

3 flagged

0.1.01.0.81.0.9

Indicators of compromise (SHA-256)

1c8996b17229185440fe7523f20f72ea848f3a001baa8946ca80fa6b5d3221ad

f2e17180cfd7a5adb5ac77241cc1c90789178a29af48fde16c66fd7a908013fd

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for gemini-analyzer (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gemini-analyzer across your stack and pipelines.
If you installed it — respond
gemini-analyzer 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.
Did it already run?
If gemini-analyzer 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.
How O3 protects you
O3 blocks gemini-analyzer 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-analyzer on PyPI has been identified as a malicious package (versions 0.1.0, 1.0.8, 1.0.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-05-gemini-analyzer

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

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

Malware detection Runtime egress monitoring