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

Yes — openaii is associated with the 2026-09-openaii 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?

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

Malicious package

openaiiPyPI

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

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

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 openaii (version 1.55.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging openaii across your stack and pipelines.
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 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 openaii 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. 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-openaii

References

bad-packages.kam193.eu

Credits

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