Which versions of private-evolution are malicious?

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

How do I remediate private-evolution if I installed it?

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

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

Yes — private-evolution is associated with the 2025-09-unicore 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 private-evolution 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 private-evolution (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 private-evolution across your stack and pipelines.

Malicious package

private-evolutionPyPI

Malicious code in private-evolution (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191817

Immediate action

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

pip uninstall private-evolution

What this malware does

Package is just calling home and there is 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: 2025-09-unicore

Reasons (based on the campaign):

other

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

82b2b994773587c9104a40a0ab5bb8d8c33a108bd2a1c409ecc7901b336eba21

b0fcdd3ad61af1881ab9e5e8b9fb871a0e142868c0be585594fcd32b5f069f6c

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for private-evolution (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 private-evolution across your stack and pipelines.
If you installed it — respond
Remove private-evolution 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 private-evolution 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 private-evolution 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. private-evolution 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-09-unicore

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks private-evolution-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