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

google-cloud-datacatalog-lineage-producer-clientPyPI

Malicious code in google-cloud-datacatalog-lineage-producer-client (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-12279
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall google-cloud-datacatalog-lineage-producer-client

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

2 flagged
999999999999

Indicators of compromise (SHA-256)

78e2603982fe3e4eb29d1da111fc4abe760e23b2d162b35d7b04063dc91d7998
73ea760146181d2911e0823c121502506892b2e63d3fc20d6281fb2c86e03de8
8bc4c59155ce2dd5d2609c5bacfb1c32de2bbea1eace2ab28d560ba2df228bc1

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 google-cloud-datacatalog-lineage-producer-client (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging google-cloud-datacatalog-lineage-producer-client across your stack and pipelines.

  2. If you installed it — respond

    google-cloud-datacatalog-lineage-producer-client 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 google-cloud-datacatalog-lineage-producer-client 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 google-cloud-datacatalog-lineage-producer-client 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. google-cloud-datacatalog-lineage-producer-client on PyPI has been identified as a malicious package (versions 9999, 99999999 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-standard-pypi-install-pentest

References

Credits

  • Kamil Mańkowski (kam193)

Detect & block this

O3 blocks google-cloud-datacatalog-lineage-producer-client-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
google-cloud-datacatalog-lineage-producer-client (PyPI) malicious package — MAL-2024-12279 | O3 Security