Which versions of getpubip are malicious?

The following PyPI versions of getpubip are flagged malicious: 0.1.0, 0.1.1, 0.1.2. Treat any of these as compromised.

How do I remediate getpubip if I installed it?

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

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

Yes — getpubip is associated with the 2026-10-getpubip 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 getpubip across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for getpubip (3 malicious versions).

Malicious package

getpubipPyPI

Advisory published Oct 15, 2026Updated Oct 15, 2026

getpubip is a confirmed malicious PyPI package (MAL-2026-17884) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1, 0.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in getpubip (PyPI)

MAL-2026-17884

Immediate action

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

pip uninstall getpubip

What this malware does

During import, obfuscated code downloads and executes an infostealer. Campaign shares some similarities with the campaign 2026-10-fontcase.

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

Campaign: 2026-10-getpubip

Reasons (based on the campaign):

Downloads and executes a remote executable.
infostealer
exfiltration-browser-data
obfuscation

Malicious versions

3 flagged

0.1.00.1.10.1.2

Indicators of compromise (SHA-256)

6a07d6dd387bbd88252ffdda7f8c10daf988f0622250daf20e7ec8ee0f63c6d5

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for getpubip (3 malicious versions).
If you installed it — respond
getpubip 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 getpubip 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. getpubip on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1, 0.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-10-getpubip

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks getpubip-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