Which versions of xwormclient are malicious?

The following PyPI versions of xwormclient are flagged malicious: 0.1.3. Treat any of these as compromised.

How do I remediate xwormclient if I installed it?

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

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

Yes — xwormclient is associated with the 2025-08-k7eel 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 xwormclient across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for xwormclient (version 0.1.3).

Part of a larger attack: 2025-08-k7eel published 31 malicious packages. See the full campaign →

Malicious package

xwormclientPyPI

Advisory published Sep 3, 2025Updated Dec 3, 2025

xwormclient is a confirmed malicious PyPI package (MAL-2025-191938) that steals credentials and exfiltrates sensitive data (malicious version 0.1.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in xwormclient (PyPI)

MAL-2025-191938

Immediate action

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

pip uninstall xwormclient

What this malware does

Importing the module downloads and executes widely recognized malware

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

Campaign: 2025-08-k7eel

Reasons (based on the campaign):

Downloads and executes a remote executable.
malware

Malicious versions

1 flagged

0.1.3

Indicators of compromise (SHA-256)

2c835756361f561034f20a019404842dcfe066ec8973a26ef4e8b3e90c6b7cbc

4a6c0b4ce2747e70d2e9f46f624188d4da6a70af3182e6e94b22de7446dc180c

Detection & response playbook

Credential / info stealer

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

Campaign

2025-08-k7eel

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

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