Which versions of my-first-pypi-demo are malicious?

The following PyPI versions of my-first-pypi-demo are flagged malicious: 0.0.1, 0.0.2, 0.0.3, 0.0.4. Treat any of these as compromised.

How do I remediate my-first-pypi-demo if I installed it?

my-first-pypi-demo 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 my-first-pypi-demo — how do I know if it already compromised me?

If my-first-pypi-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 my-first-pypi-demo part of a known attack campaign?

Yes — my-first-pypi-demo is associated with the RLMA-2025-05623, GENERIC-standard-pypi-install-pentest, RLUA-2026-00546 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 my-first-pypi-demo across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for my-first-pypi-demo (4 malicious versions).

Malicious package

my-first-pypi-demoPyPI

Advisory published Aug 20, 2025Updated Mar 19, 2026

my-first-pypi-demo is a confirmed malicious PyPI package (MAL-2025-191651) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.1, 0.0.2, 0.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in my-first-pypi-demo (PyPI)

MAL-2025-191651

Immediate action

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

pip uninstall my-first-pypi-demo

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

4 flagged

0.0.10.0.20.0.30.0.4

Indicators of compromise (SHA-256)

b75c5a6d41769cadde9f279da0cd7eacb4e61ffac9e11a8343c01d6c6c4dd103

e3ccc59ce3b3f0670ad2c04524e962d6a43f562433b082fc808db1fadb41c87d

f789a8192ed7a62a0fa9327e495ac8ca2658ff556673ca8d207f7954204ec160

828df3441db1954c300016f9af096196472db8754efa2f716f9cfe28f219144f

0815a9846194ee85f084fcc59c9fbcf6157f4d1453bdda05535a73e9d23a347f

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for my-first-pypi-demo (4 malicious versions).
If you installed it — respond
my-first-pypi-demo 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 my-first-pypi-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. my-first-pypi-demo on PyPI has been identified as a malicious package (versions 0.0.1, 0.0.2, 0.0.3, 0.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05623GENERIC-standard-pypi-install-pentestRLUA-2026-00546

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks my-first-pypi-demo-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