# MAL-2026-17884: Malicious code in getpubip (PyPI)


- **Type:** Malicious package
- **Package:** `getpubip` (PyPI)
- **Published:** 15 Oct 2026

## What is MAL-2026-17884?

MAL-2026-17884 is a malicious package in getpubip, published on 15 Oct 2026. 

### Official description

getpubip/__init__.py runs exec() on an approximately 2KB opaque payload produced by reversing a string literal, base64-decoding it, and zlib-decompressing it (lambda __: __import__('zlib').decompress(__import__('base64').b64decode(__[::-1])); exec(_(b'...'))). The package advertises itself as a three-line helper that returns the host's public IP by calling ipify, and a clean implementation of that functionality exists in core.py; __init__.py does not re-export get_ip and its only effect on import is to execute the hidden blob. The payload is reached whenever a consumer runs `import getpubip` or `python -m getpubip`, so any installer that uses the package executes the concealed code with no further user action. The triple-layered obfuscation (string reverse, base64, zlib) and single-character identifiers are deliberately chosen to hide the executed code from reviewers; whatever the decoded bytes do runs in the installer's process on first import.

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

## What should I do about MAL-2026-17884?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-17884 is a malicious package: getpubip (PyPI). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-17884/ (Markdown: https://insights.sbomify.com/MAL-2026-17884/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-17884

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-17884/
Summaries are generated and may contain mistakes; the official description above is the record.