Which versions of klsosdoids2 are malicious?

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

How do I remediate klsosdoids2 if I installed it?

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

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

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

Malicious package

klsosdoids2PyPI

Malicious code in klsosdoids2 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191776

Immediate action

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

pip uninstall klsosdoids2

What this malware does

Package simulates malicious activity during installation and 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)

09d9aaf3acacb6ff779fc6cd8be31c7208270d5178486a02b114dcae06330615

d72d2891383419bc38738c4c3be786e31a5000e46d5b3064bacf11561ad69af8

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for klsosdoids2 (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging klsosdoids2 across your stack and pipelines.
If you installed it — respond
Remove klsosdoids2 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 klsosdoids2 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 klsosdoids2 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. klsosdoids2 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 klsosdoids2-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