Which versions of private-test-4 are malicious?

The following PyPI versions of private-test-4 are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate private-test-4 if I installed it?

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

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

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

Malicious package

private-test-4PyPI

Malicious code in private-test-4 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-955

Immediate action

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

pip uninstall private-test-4

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

1.0.1

Indicators of compromise (SHA-256)

4b51034370aa4169b92f8b3cd80f666063d4b2d91e21f3ae7f68254a8a7cbf3e

7cbcad497e09d6c5a1be26bf9fc17cbd69a5cde25bb940e690b6c37471a5e608

e4dd4ce4306e9d9704fdbbf2b63e86ca01614fee5f263dbb208c79986a14c334

1eecade0df32bc01566010bb1df0c137c7f3fb72c9fdcf029688f768d7c0a0c2

4f1f063d97fe98dbcf747617f0418ada9f10407d035a4e66e7bd1a0c8bfdb5cf

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

Campaign

RLMA-2025-00496GENERIC-standard-pypi-install-pentestRLUA-2026-00607

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks private-test-4-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