Which versions of testpackageroietest3 are malicious?

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

How do I remediate testpackageroietest3 if I installed it?

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

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

Yes — testpackageroietest3 is associated with the RLMA-2025-04274, GENERIC-standard-pypi-install-pentest, RLUA-2026-00810 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 testpackageroietest3 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 testpackageroietest3 (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 testpackageroietest3 across your stack and pipelines.

Malicious package

testpackageroietest3PyPI

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

MAL-2025-41776

Immediate action

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

pip uninstall testpackageroietest3

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)

bfec688e696037e08030bbef0738e4ef4a305aa1764d8006c8c642784da6f6f7

2dbc78946dd1784d28588d022c5e07e7826fbb761b03ff380227c7518333d26f

88b61508de8bb1a4224db6f1b2c7f8784f678f59e6ecacfac77c0a7d3f0409df

2b5485638bb8d1c5fcea312849dc503276dd2f46df29353c1003d1df45881584

b8e13e25906d504b5f9c9fb86de8bc8eb18e502a66723c2868832423129f85b0

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 testpackageroietest3 (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 testpackageroietest3 across your stack and pipelines.
If you installed it — respond
testpackageroietest3 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 testpackageroietest3 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 testpackageroietest3 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. testpackageroietest3 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-04274GENERIC-standard-pypi-install-pentestRLUA-2026-00810

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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