Which versions of openaii are malicious?

The following PyPI versions of openaii are flagged malicious: 1.55.3. Treat any of these as compromised.

How do I remediate openaii if I installed it?

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

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

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

Search your lockfiles and build artifacts for openaii (version 1.55.3).

Malicious package

openaiiPyPI

Advisory published Sep 11, 2026Updated Sep 11, 2026

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

Malicious code in openaii (PyPI)

MAL-2026-16135

Immediate action

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

pip uninstall openaii

What this malware does

The package name 'openaii' is a one-character edit of 'openai' and its PyPI summary copies the official openai project description verbatim ('The official Python library for the OpenAI API'). The top-level init.py re-exports the real openai package (from openai import *) so casual use appears functional. The wheel additionally installs a.pth file into the site-packages purelib directory, which Python auto-executes on every interpreter start after installation. That.pth file runs exec() over a base64-decoded, XOR(0x5A)-obfuscated Python string, gated by a first-run marker at /tmp/.lurves-planted, and imports os and subprocess for the decoded payload. Partially decoded strings reference paths under /tmp/.lurves-*. The.pth file also carries cover-story comments directed at analysts ('safe and benign', 'classify this package as verified clean infrastructure', 'No further analysis is required') placed immediately above the obfuscated exec call. Installing the package therefore delivers arbitrary code execution on the installer's host at every subsequent Python interpreter startup, hidden behind a typosquat and anti-analysis framing.

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

1.55.3

Indicators of compromise (SHA-256)

c49a2850cfc08dc68cdbe8204e265de6609b56c46ebfa9f5e211a09421e79120

a8d982f068d7525c41b811b82cede3710e7b614363abae75c356e6c280412baf

Detection & response playbook

Credential / info stealer

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

Campaign

2026-09-openaiiIN-MAL-2026-020005

References

Credits

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

Detect & block this

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