Which versions of benign-lib are malicious?

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

How do I remediate benign-lib if I installed it?

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

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

Yes — benign-lib is associated with the RLMA-2025-05587, 2025-10-benign-lib, RLUA-2026-00142 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 benign-lib across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for benign-lib (version 1.0.0).

Malicious package

benign-libPyPI

Advisory published Oct 25, 2025Updated Mar 19, 2026

benign-lib is a confirmed malicious PyPI package (MAL-2025-191620) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in benign-lib (PyPI)

MAL-2025-191620

Immediate action

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

pip uninstall benign-lib

What this malware does

Package hides an executable inside, and starts it when imported. The sandbox analysis shows only starting a calculator, which suggests it's a research attempt without a big harm.

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-10-benign-lib

Reasons (based on the campaign):

malware
obfuscation

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

376aeae73b37815142b47e2fba740d180196b7e5f760475ae3333b3e87bc4d70

dde05c4a0256dc32b25188e40f8bd2b4d3e3348cea23c0160994d46728c4c6bb

09477b048d84611002417894ccb3265d246be0156b096a8b47776960d45e9d3d

f6eb37889a0b4202f01adc7be269de32a85f22a72b4b9e490808e94d20f85ff6

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for benign-lib (version 1.0.0).
If you installed it — respond
Remove benign-lib 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 benign-lib 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. benign-lib 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

RLMA-2025-055872025-10-benign-libRLUA-2026-00142

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks benign-lib-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