Which versions of klsosdoids5 are malicious?

The following PyPI versions of klsosdoids5 are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate klsosdoids5 if I installed it?

Remove klsosdoids5 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed klsosdoids5 — how do I know if it already compromised me?

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

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

Search your lockfiles and build artifacts for klsosdoids5 (version 0.1).

Part of a larger attack: 2025-10-wangzhou183 published 19 malicious packages. See the full campaign →

Malicious package

klsosdoids5PyPI

Advisory published Oct 19, 2025Updated Dec 3, 2025

klsosdoids5 is a confirmed malicious PyPI package (MAL-2025-191777) that executes malicious code on install (malicious version 0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in klsosdoids5 (PyPI)

MAL-2025-191777

Immediate action

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

pip uninstall klsosdoids5

What this malware does

Package simulates calling home on import and there has no other purpose

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2025-10-wangzhou183

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

0229f7e54969cd6d769e1c8e66c89efceb054eb9a5b6e4e5bdb9933f6aba6d8c

9463b9f77f9d64f5acb9c6a75b2969333be89d6d850af7e75628532ff23e0641

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for klsosdoids5 (version 0.1).
If you installed it — respond
Remove klsosdoids5 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If klsosdoids5 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. klsosdoids5 on PyPI has been identified as a malicious package (version 0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-10-wangzhou183

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks klsosdoids5-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database