Which versions of malicious-pip-package-for-demo are malicious?

The following PyPI versions of malicious-pip-package-for-demo are flagged malicious: 1.0.2, 1.0.3, 1.0.4. Treat any of these as compromised.

How do I remediate malicious-pip-package-for-demo if I installed it?

Remove malicious-pip-package-for-demo from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed malicious-pip-package-for-demo — how do I know if it already compromised me?

If malicious-pip-package-for-demo 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 malicious-pip-package-for-demo part of a known attack campaign?

Yes — malicious-pip-package-for-demo is associated with the RLMA-2025-04195 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 malicious-pip-package-for-demo across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for malicious-pip-package-for-demo (3 malicious versions).

Malicious package

malicious-pip-package-for-demoPyPI

malicious-pip-package-for-demo is a confirmed malicious PyPI package (MAL-2025-41700) that executes malicious code on install (malicious versions 1.0.2, 1.0.3, 1.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in malicious-pip-package-for-demo (PyPI)

MAL-2025-41700

Immediate action

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

pip uninstall malicious-pip-package-for-demo

Malicious versions

3 flagged

1.0.21.0.31.0.4

Indicators of compromise (SHA-256)

51a2def172c45ce0a9c3363eaf389ad63680b355a10b519780d1400ff17448d0

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for malicious-pip-package-for-demo (3 malicious versions).
If you installed it — respond
Remove malicious-pip-package-for-demo from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If malicious-pip-package-for-demo 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. malicious-pip-package-for-demo on PyPI has been identified as a malicious package (versions 1.0.2, 1.0.3, 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04195

Credits

ReversingLabs · finder

Detect & block this

O3 blocks malicious-pip-package-for-demo-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database