Which versions of googleapis-googleapis-grpc-python are malicious?

The following PyPI versions of googleapis-googleapis-grpc-python are flagged malicious: 1.9.3. Treat any of these as compromised.

How do I remediate googleapis-googleapis-grpc-python if I installed it?

googleapis-googleapis-grpc-python 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 googleapis-googleapis-grpc-python — how do I know if it already compromised me?

If googleapis-googleapis-grpc-python 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 googleapis-googleapis-grpc-python part of a known attack campaign?

Yes — googleapis-googleapis-grpc-python is associated with the RLMA-2025-01217, GENERIC-standard-pypi-install-pentest, RLUA-2026-00360 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 googleapis-googleapis-grpc-python 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 googleapis-googleapis-grpc-python (version 1.9.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging googleapis-googleapis-grpc-python across your stack and pipelines.

Malicious package

googleapis-googleapis-grpc-pythonPyPI

Malicious code in googleapis-googleapis-grpc-python (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-1976

Immediate action

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

pip uninstall googleapis-googleapis-grpc-python

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

1.9.3

Indicators of compromise (SHA-256)

e33d08e7a3db19084900806cc885ae1b134d93beb8f1686dd86a237c383ec980

dd7b59b3a0a0558453dfc8a0c2fbe51dfa57ef80f6466d06b86ea77486d2383b

0173c52d763cfc2d6f3c0222ad82887aa50ee181e8cfe807aa700d34cc54fb45

437fc060336b54c207ceca942fe31ad7abd6d0fa565d2bb45bf7c9a9a2a1fa0d

cd64a809cce548d7ab1304a4254ce287c846651359fb05712c970005b57cb0c1

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 googleapis-googleapis-grpc-python (version 1.9.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging googleapis-googleapis-grpc-python across your stack and pipelines.
If you installed it — respond
googleapis-googleapis-grpc-python 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 googleapis-googleapis-grpc-python 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 googleapis-googleapis-grpc-python 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. googleapis-googleapis-grpc-python on PyPI has been identified as a malicious package (version 1.9.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-01217GENERIC-standard-pypi-install-pentestRLUA-2026-00360

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks googleapis-googleapis-grpc-python-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