Which versions of veloxml-cli are malicious?

The following PyPI versions of veloxml-cli are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate veloxml-cli if I installed it?

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

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

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

Search your lockfiles and build artifacts for veloxml-cli (version 0.1.0).

Malicious package

veloxml-cliPyPI

Advisory published May 28, 2026Updated May 28, 2026

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

Malicious code in veloxml-cli (PyPI)

MAL-2026-4862

Immediate action

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

pip uninstall veloxml-cli

What this malware does

The package advertises fake functionality and exfiltrates the given email and basic information about the host when used.

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

Campaign: 2026-05-veloxml-cli

Reasons (based on the campaign):

action-hidden-in-lib-usage
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

57a2b332595fb95752df25e794528ff2dd610bf3977b8d4abd7574cb0f21cdff

Detection & response playbook

Credential / info stealer

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

Campaign

2026-05-veloxml-cli

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks veloxml-cli-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