Which versions of testpackageroietest2 are malicious?

The following PyPI versions of testpackageroietest2 are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate testpackageroietest2 if I installed it?

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

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

Yes — testpackageroietest2 is associated with the RLMA-2025-04273, GENERIC-standard-pypi-install-pentest, RLUA-2026-00809 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 testpackageroietest2 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 testpackageroietest2 (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging testpackageroietest2 across your stack and pipelines.

Malicious package

testpackageroietest2PyPI

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

MAL-2025-41775

Immediate action

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

pip uninstall testpackageroietest2

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package 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: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5d6280bafd371680c1e4527f6b8cb8cc2ca15ba79a4972c50e57251e00b5bf11

4fac6ea416efdbdd66fdb6ce65d38b0f9d865821c5010df81da5b94e82fb2f49

540d9028178695a791b307758df0ac5dca1f6c77f19e12579e4b0745580f358d

f20f64c0ca3c64dbc9462db2d81e5b6e4215f48bd09d2582fbc7bee3a887ecae

0bfe4b80c6d7a40761bf2283c7c12464a5b732580ba3e18bb9691ce2dbb2a8b1

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

Campaign

RLMA-2025-04273GENERIC-standard-pypi-install-pentestRLUA-2026-00809

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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