Which versions of kirux189894 are malicious?

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

How do I remediate kirux189894 if I installed it?

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

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

Yes — kirux189894 is associated with the RLMA-2025-05613, 2025-10-wangzhou183, RLUA-2026-00454 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 kirux189894 across my projects, lockfiles, and CI pipelines?

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

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

Malicious package

kirux189894PyPI

Advisory published Oct 19, 2025Updated Mar 19, 2026

kirux189894 is a confirmed malicious PyPI package (MAL-2025-191642) 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 kirux189894 (PyPI)

MAL-2025-191642

Immediate action

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

pip uninstall kirux189894

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)

7cb5b563328257581931a74c2c391cf5b3fbbca32c3894a0c7cb4002c48f5471

a706f83e7abbadbb116431c5616c48433645df5f4feb868daa8b174d9e428b8c

f147ce226cffa7d6f6b34db801242958dc198c8d18c01cef735b65439dae8678

2bf48abe6c512f80de104d3a28f2c32eb056d97d45968946f3fb3d384d984596

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for kirux189894 (version 0.1).
If you installed it — respond
Remove kirux189894 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 kirux189894 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. kirux189894 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

RLMA-2025-056132025-10-wangzhou183RLUA-2026-00454

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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