Which versions of infra-libs are malicious?

The following PyPI versions of infra-libs are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate infra-libs if I installed it?

infra-libs 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 infra-libs — how do I know if it already compromised me?

If infra-libs was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is infra-libs part of a known attack campaign?

Yes — infra-libs is associated with the IN-MAL-2026-022565, GENERIC-standard-pypi-install-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 infra-libs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for infra-libs (version 99.99.99).

Malicious package

infra-libsPyPI

Advisory published Nov 8, 2026Updated Nov 8, 2026

infra-libs is a confirmed malicious PyPI package (MAL-2026-18761) that steals credentials and exfiltrates sensitive data (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in infra-libs (PyPI)

MAL-2026-18761

Immediate action

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

pip uninstall infra-libs

What this malware does

infra-libs 99.99.99 performs install-time and import-time DNS exfiltration of the installer's hostname. setup.py constructs a subdomain label of the form install-<random-id>-<hostname> and calls socket.getaddrinfo against <label>.testa213022.dssldrf.net, causing the authoritative name server for that zone to receive the installer's platform.node() value during pip install. gcp_log_poc/init.py repeats the same pattern with an import-<id>-<hostname> label on every import of the package, and the module docstring explicitly describes the behavior as a 'DNS callback on import.' The destination domain testa213022.dssldrf.net is unrelated to any declared publisher or purpose, the package has no documented functionality that would justify a hostname-encoded DNS lookup, and the name infra-libs is confusable with internal/infrastructure naming conventions commonly targeted by dependency-confusion attacks. No legitimate behavior accompanies the beacon.

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

99.99.99

Indicators of compromise (SHA-256)

721b376b505d760e78f3ac8417b54789f538a5a8127f59fe7c2660067366ce32

2796ca84a4fd5c8e195f4b1a5cd7ce752c3a13c34e015ea1ce0436a2774c3b8d

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for infra-libs (version 99.99.99).
If you installed it — respond
infra-libs 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 infra-libs was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. infra-libs on PyPI has been identified as a malicious package (version 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022565GENERIC-standard-pypi-install-pentest

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks infra-libs-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

Explore

All malware advisories How O3 detects malware Vulnerability database