What does the grpc-google-bigtable-v2 malware do?

Generic campaign for all (likely) research / pentests, where the amount or art of collected data raises questions about the privacy, security and ethical side. Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: GENERIC-questionable-pentest Reasons (based on the campaign): - exfiltration-env-variables - exfiltration-generic - The package overrides the install command in setup.py to execute malicious code during installation. - typosquatting The OpenSSF Package Analysis project identified 'grpc-google-bigtable-v2' @ 0.11.99 (pypi) as malicious. It is considered malicious because: - The package communicates with a domain associated with m

Which versions of grpc-google-bigtable-v2 are malicious?

The following PyPI versions of grpc-google-bigtable-v2 are flagged malicious: 0.11.99. Treat any of these as compromised.

How do I remediate grpc-google-bigtable-v2 if I installed it?

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

If grpc-google-bigtable-v2 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 grpc-google-bigtable-v2 part of a known attack campaign?

Yes — grpc-google-bigtable-v2 is associated with the RLMA-2025-03611, GENERIC-questionable-pentest 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 grpc-google-bigtable-v2 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 grpc-google-bigtable-v2 (version 0.11.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging grpc-google-bigtable-v2 across your stack and pipelines.

Malicious package

grpc-google-bigtable-v2PyPI

Malicious code in grpc-google-bigtable-v2 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-4665

Immediate action

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

pip uninstall grpc-google-bigtable-v2

What this malware does

Generic campaign for all (likely) research / pentests, where the amount or art of collected data raises questions about the privacy, security and ethical side.

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

Campaign: GENERIC-questionable-pentest

Reasons (based on the campaign):

exfiltration-env-variables
exfiltration-generic
The package overrides the install command in setup.py to execute malicious code during installation.
typosquatting

The OpenSSF Package Analysis project identified 'grpc-google-bigtable-v2' @ 0.11.99 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

0.11.99

Indicators of compromise (SHA-256)

ede9be184ad678c156e8b6fa9edc4acb9fba416bbb0f0a67b243da2476ea8e3f

4133c2dfc12e97646c8cd2927d819ed1fdcd52656b080407a12b28d6295f9dd3

fc0b270abbfe9d697c61881d94b198b88069a76825ca24a48d35425db14e9232

9640f0015404a6fff13b4e9bbb9e01d3d4f545a8ae8935dc95425a427c561576

ebc6b767fb6cd105f3a0771ef6a2c27b3d89a4242abdd0654af36c5fc8dee3f9

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

Campaign

RLMA-2025-03611GENERIC-questionable-pentest

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

O3 blocks grpc-google-bigtable-v2-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