Which versions of matplotliv are malicious?

The following PyPI versions of matplotliv are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate matplotliv if I installed it?

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

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

Yes — matplotliv is associated with the 2025-09-matplotliv 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 matplotliv across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for matplotliv (version 0.1.0).

Malicious package

matplotlivPyPI

Advisory published Sep 26, 2025Updated Dec 3, 2025

matplotliv is a confirmed malicious PyPI package (MAL-2025-191787) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in matplotliv (PyPI)

MAL-2025-191787

Immediate action

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

pip uninstall matplotliv

What this malware does

Typosqatting package collecting, but not exfiltrating (thus fulfiling the educational promise), sensitive data

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: 2025-09-matplotliv

Reasons (based on the campaign):

typosquatting

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

6b3f06d28b98caec89b92e9d51032bad69993a62a73802a54fedc14d77f5f535

491ff5ae8247837ff9be18d46366f453395dab2413f44f6251aff0b271f7d25b

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for matplotliv (version 0.1.0).
If you installed it — respond
matplotliv 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 matplotliv 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. matplotliv on PyPI has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-09-matplotliv

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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