Which versions of private-test-1 are malicious?

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

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

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

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

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

Malicious package

private-test-1PyPI

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

MAL-2025-953

Immediate action

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

pip uninstall private-test-1

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

Indicators of compromise (SHA-256)

f9ada75e893f2910458e09e6d6fa4f7a4b293c6ba29daf79d425f82f55e6bfa2

7801d13e913f431944d5b1d84346dc67046dbea690eb0f3505e87f2ac4912a67

d02d81970f5f0499cbb8367bbf818511b5183733b38ea9b0fa35a6b46d2912f3

6abff31067d291e3c3773a6d6762cbd8c9e2d07da243c31acac17ca024af3d54

fa52b91a546a341d318ebca30bb2c8983107916e79b66dc6f346802fc032ebb0

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

Campaign

RLMA-2025-00494GENERIC-standard-pypi-install-pentestRLUA-2026-00605

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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