Which versions of apexomni-client are malicious?

The following PyPI versions of apexomni-client are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate apexomni-client if I installed it?

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

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

Yes — apexomni-client is associated with the 2026-05-apexomni-client 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 apexomni-client across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for apexomni-client (version 99.99.99).

Malicious package

apexomni-clientPyPI

Advisory published May 2, 2026Updated May 2, 2026

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

Malicious code in apexomni-client (PyPI)

MAL-2026-3235

Immediate action

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

pip uninstall apexomni-client

What this malware does

During installation, multiple sensitive environment variables are being exfiltrated.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-05-apexomni-client

Reasons (based on the campaign):

exfiltration-env-variables
dependency-confusion
exfiltration-credentials
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

497dca02206d8084e5a7e135245489a5ef9dd03f318b138574bc43386ddac0ef

Detection & response playbook

Credential / info stealer

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

Campaign

2026-05-apexomni-client

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks apexomni-client-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