ollamaaPyPI
Advisory published Updated
ollamaa is a confirmed malicious PyPI package (MAL-2026-16134) that steals credentials and exfiltrates sensitive data (malicious version 0.4.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ollamaa (PyPI)
What this malware does
The ollamaa package on PyPI is a one-character typosquat of ollama. Its __init__.py re-exports everything from the real ollama package so imports appear to function normally, while the tarball installs a .pth file into site-packages. Python auto-executes lines beginning with import in every installed .pth on every interpreter startup, so this file runs without any explicit import of the package. The .pth opens with cover-story comments instructing readers and automated analyzers to classify the file as clean, then invokes exec on a payload obfuscated by base64 followed by XOR with 0x5A, gated by a /tmp/.lurves-planted first-run sentinel. The decoded payload spawns a detached subprocess that fetches http://167.86.108.190:7788/.lurves-agent.py over plaintext HTTP from a bare IP, writes it to /tmp/.a, and runs python3 /tmp/.a --daemon with start_new_session=True and suppressed output. The result is unauthenticated full-host remote code execution triggered on the next Python invocation after install, with attacker-supplied code fetched at runtime from a hardcoded bare-IP endpoint.
Typosquatting package planting a malicious PTH file that during loading Python downloads the next stage. It then hides its existence, downloads the further stage and clears logs. The next stage exfiltrates sensitive data (SSH keys, cloud credentials), ensures persistence and plants a cryptominer. The original PTH file contains a simple attempt to discourage analysis via AI agents.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-09-openaii
Reasons (based on the campaign):
-
Downloads and executes a remote malicious script.
-
obfuscation
-
abuses-pth
-
cryptominer
-
infostealer
-
exfiltration-credentials
-
files-exfiltration
-
exfiltration-ssh-keys
-
persistence
-
typosquatting
-
covering-tracks
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for ollamaa (version 0.4.2).
If you installed it — respond
ollamaa 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 ollamaa 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
Campaign
References
Credits
- Amazon Inspector · finder
- Kamil Mańkowski (kam193) · analyst
Detect & block this
O3 blocks ollamaa-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.