Which versions of matplotlibe are malicious?

The following PyPI versions of matplotlibe are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate matplotlibe if I installed it?

matplotlibe is a typosquat — you almost certainly intended a legitimately-named package. Remove matplotlibe, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed matplotlibe — how do I know if it already compromised me?

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

Yes — matplotlibe is associated with the 2025-05- yesyesyes 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 matplotlibe 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 matplotlibe (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging matplotlibe across your stack and pipelines.

Malicious package

matplotlibePyPI

Malicious code in matplotlibe (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191786

Immediate action

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

pip uninstall matplotlibe

What this malware does

Clearly typosquatting packages, but no known malicious parts.

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-05- yesyesyes

Reasons (based on the campaign):

typosquatting

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

f8d5c031507163d88d91b038d4d2bbd73565125b93059a5bb96243072445caec

082b8eb9ac76b7c5ec057f8c5f0aeff99b84841c33c50fb570874ff4e435375a

a039d815ef7ca48b52d2a53be83fce00ce9e8aefc20c4ad0003c97d9d61b84ea

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for matplotlibe (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging matplotlibe across your stack and pipelines.
If you installed it — respond
matplotlibe is a typosquat — you almost certainly intended a legitimately-named package. Remove matplotlibe, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If matplotlibe 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 matplotlibe 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. matplotlibe on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-05- yesyesyes

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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