Which versions of raknet-testing-package2 are malicious?

The following PyPI versions of raknet-testing-package2 are flagged malicious: 0.0.1, 0.0.2, 0.0.3. Treat any of these as compromised.

How do I remediate raknet-testing-package2 if I installed it?

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

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

Yes — raknet-testing-package2 is associated with the RLMA-2025-04225, 2025-08-raknet-testing-package, RLUA-2026-00682 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 raknet-testing-package2 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 raknet-testing-package2 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging raknet-testing-package2 across your stack and pipelines.

Malicious package

raknet-testing-package2PyPI

Malicious code in raknet-testing-package2 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-41730

Immediate action

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

pip uninstall raknet-testing-package2

What this malware does

During installation, the package attempts to install the own MITM proxy without user's consent and hijack all requests

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

Campaign: 2025-08-raknet-testing-package

Reasons (based on the campaign):

exfiltration-generic
modify-system-without-consent

Malicious versions

3 flagged

0.0.10.0.20.0.3

Indicators of compromise (SHA-256)

6f90ae084ea91ce35479aa81764ce04e5a246e7e312641cdb234d253e86cc355

852b05599daad3eab8e83de977a3811f229696e061e7a6208865bda3f496f65f

d26ae7cefa4b8ebaf16a44f6d3c42c1fd6dbacda884e5b03b06da5ff237d7435

b3d8492ebc82bc9abf6f3f974bd5afe0416e079db2e23f4e04fe7e0f6256fa6f

2afb41fc9e80175d990f5478fd3a9d8d21d9242228dfcd27ff4abe50fb94e480

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 raknet-testing-package2 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging raknet-testing-package2 across your stack and pipelines.
If you installed it — respond
raknet-testing-package2 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 raknet-testing-package2 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 raknet-testing-package2 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. raknet-testing-package2 on PyPI has been identified as a malicious package (versions 0.0.1, 0.0.2, 0.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-042252025-08-raknet-testing-packageRLUA-2026-00682

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks raknet-testing-package2-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