Which versions of rtpoc1 are malicious?

The following PyPI versions of rtpoc1 are flagged malicious: 0.1, 0.2. Treat any of these as compromised.

How do I remediate rtpoc1 if I installed it?

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

If rtpoc1 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is rtpoc1 part of a known attack campaign?

Yes — rtpoc1 is associated with the GENERIC-standard-pypi-install-pentest 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 rtpoc1 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for rtpoc1 (2 malicious versions).

Malicious package

rtpoc1PyPI

Advisory published Jul 26, 2024Updated Dec 12, 2025

rtpoc1 is a confirmed malicious PyPI package (MAL-2025-36) that steals credentials and exfiltrates sensitive data (malicious versions 0.1, 0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rtpoc1 (PyPI)

MAL-2025-36

Immediate action

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

pip uninstall rtpoc1

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.

The OpenSSF Package Analysis project identified 'rtpoc1' @ 0.2 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

0.10.2

Indicators of compromise (SHA-256)

167f71321a3854879568e4d1e2caaebc490967f77f2f1a949123ce5c6ceae8fe

159a77f271d6737225ca42c80a21d42af0856560084e94c815b9c1248225d748

6fec3cb3c9354af29d7edbc82703c0fe7406084014bd610bd383ee2795d324ca

4f5e49ec135224dbd62998a497d55bedb51feaff441f32772430699dad397e37

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for rtpoc1 (2 malicious versions).
If you installed it — respond
rtpoc1 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 rtpoc1 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. rtpoc1 on PyPI has been identified as a malicious package (versions 0.1, 0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-standard-pypi-install-pentest

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database