Which versions of this-is-poc-fortesting-dontinstall-12345 are malicious?

The following PyPI versions of this-is-poc-fortesting-dontinstall-12345 are flagged malicious: 0.0.1, 0.0.3. Treat any of these as compromised.

How do I remediate this-is-poc-fortesting-dontinstall-12345 if I installed it?

this-is-poc-fortesting-dontinstall-12345 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 this-is-poc-fortesting-dontinstall-12345 — how do I know if it already compromised me?

If this-is-poc-fortesting-dontinstall-12345 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 this-is-poc-fortesting-dontinstall-12345 part of a known attack campaign?

Yes — this-is-poc-fortesting-dontinstall-12345 is associated with the RLMA-2024-09415, GENERIC-standard-pypi-install-pentest, RLUA-2026-00818 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 this-is-poc-fortesting-dontinstall-12345 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 this-is-poc-fortesting-dontinstall-12345 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging this-is-poc-fortesting-dontinstall-12345 across your stack and pipelines.

Malicious package

this-is-poc-fortesting-dontinstall-12345PyPI

Malicious code in this-is-poc-fortesting-dontinstall-12345 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-10174

Immediate action

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

pip uninstall this-is-poc-fortesting-dontinstall-12345

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

2 flagged

0.0.10.0.3

Indicators of compromise (SHA-256)

8d58642828d107435bf0b222810ec9512595db8c795033d277d654de6c9fbc10

fecee3eb2ddb01da713a307ebc258c30892c10d6b505e719b356713e1ca92b38

6731f0b45ddfd51d7b4ede3181c38007a58a01e569b13d867b987cd9487ee472

01594393ac783656dbec4f24a6b034de4747e19d72acd53200e1132bab352b02

fe792efb6b6b9feb135c890065e9253daa0ff53ddde890d2be8e9388fcaf169b

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

Campaign

RLMA-2024-09415GENERIC-standard-pypi-install-pentestRLUA-2026-00818

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks this-is-poc-fortesting-dontinstall-12345-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