Which versions of ollamaa are malicious?

The following PyPI versions of ollamaa are flagged malicious: 0.4.2. Treat any of these as compromised.

How do I remediate ollamaa if I installed it?

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.

I already installed ollamaa — how do I know if it already compromised me?

If ollamaa 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.

Is ollamaa part of a known attack campaign?

Yes — ollamaa is associated with the 2026-09-openaii, IN-MAL-2026-020007 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 ollamaa across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ollamaa (version 0.4.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ollamaa across your stack and pipelines.

Malicious package

ollamaaPyPI

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)

MAL-2026-16134

Immediate action

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

pip uninstall ollamaa

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

1 flagged

0.4.2

Indicators of compromise (SHA-256)

bdddd369c97996ed3c886729053c3f8189bf96bc22914f2c61c901b3e96073fc

11eb7019f9ead481b3c5f203703df3b8b63abab2e03502a02ba30360da9948d9

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ollamaa (version 0.4.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ollamaa across your stack and pipelines.
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 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.
How O3 protects you
O3 blocks ollamaa 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. ollamaa on PyPI has been identified as a malicious package (version 0.4.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-09-openaiiIN-MAL-2026-020007

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database