What does the anku2-rce malware do?

Installing starts a reverse shell Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2025-07-anku2-rce Reasons (based on the campaign): - The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine. - The package overrides the install command in setup.py to execute malicious code during installation.

Which versions of anku2-rce are malicious?

The following PyPI versions of anku2-rce are flagged malicious: 0.0.1, 0.0.2. Treat any of these as compromised.

How do I remediate anku2-rce if I installed it?

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

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

Yes — anku2-rce is associated with the RLMA-2025-03517, 2025-07-anku2-rce, RLUA-2026-00066 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 anku2-rce 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 anku2-rce (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging anku2-rce across your stack and pipelines.

Malicious package

anku2-rcePyPI

Malicious code in anku2-rce (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-6433

Immediate action

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

pip uninstall anku2-rce

What this malware does

Installing starts a reverse shell

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

Campaign: 2025-07-anku2-rce

Reasons (based on the campaign):

The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

2314ca216dbc96a88bbe41d29146515491f6ea18243de5c7b404c3c605b18397

8316954c2bde1e576829dee228a7192007fdbc98382233f0a9aa243b804b19fa

4a0fdfa7bc3195d177e4d6e3dcad16eb59cc436e2b4dc48230b0c088546086fe

8cd81237a7437dc22233c906893fe125b9a8f3b14907db395a7034e018846c4d

b2f0675a57d584aecf57d04f037bdd37951db34d74fd7ff3f651bbde1f189986

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for anku2-rce (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging anku2-rce across your stack and pipelines.
If you installed it — respond
anku2-rce 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 anku2-rce 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 anku2-rce 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. anku2-rce on PyPI has been identified as a malicious package (versions 0.0.1, 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-035172025-07-anku2-rceRLUA-2026-00066

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks anku2-rce-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