Which versions of testpackageroietest4 are malicious?

The following PyPI versions of testpackageroietest4 are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate testpackageroietest4 if I installed it?

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

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

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

Malicious package

testpackageroietest4PyPI

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

MAL-2025-41777

Immediate action

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

pip uninstall testpackageroietest4

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.1.0

Indicators of compromise (SHA-256)

e71672a098b2fa703ef68f3591fdd9014a2770f03230fabf96642c22939d96df

2bbb2f5facb643eeb097b472758aefaf1b8e864aa972a8878dcbc4dbde0dc173

8513ccd29444557d2b772e8c39dcbac59fc00b022d9119643a3b8dc9906585b1

047368051fe20f32440ec0f9c6277b9c815919a9e8fb079f9994f14439ab088f

52be0b1ad27ed53819bc504d7acc60c8d402ae993868338e5dccd8c87bf3deb6

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

Campaign

RLMA-2025-04275GENERIC-standard-pypi-install-pentestRLUA-2026-00811

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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