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

hpe-glcp-automation-libPyPI

Malicious code in hpe-glcp-automation-lib (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-5183
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall hpe-glcp-automation-lib

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
2.2160.0

Indicators of compromise (SHA-256)

53256c57763ad4be286cf74bf0162b67413edc085338e3778ac9bc2afa1b4b93

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 hpe-glcp-automation-lib (version 2.2160.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hpe-glcp-automation-lib across your stack and pipelines.

  2. If you installed it — respond

    hpe-glcp-automation-lib 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 hpe-glcp-automation-lib 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 hpe-glcp-automation-lib 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. hpe-glcp-automation-lib on PyPI has been identified as a malicious package (version 2.2160.0 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) · reporter

Detect & block this

O3 blocks hpe-glcp-automation-lib-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
hpe-glcp-automation-lib (PyPI) malicious package — MAL-2026-5183 | O3 Security