Which versions of unicore are malicious?

The following PyPI versions of unicore are flagged malicious: 1.1.0, 1.2.0, 2, 2.0.0, 2.0.1. Treat any of these as compromised.

How do I remediate unicore if I installed it?

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

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

Yes — unicore 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 unicore across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for unicore (5 malicious versions).

Malicious package

unicorePyPI

Advisory published Sep 7, 2025Updated Apr 22, 2026

unicore is a confirmed malicious PyPI package (MAL-2025-191916) that executes malicious code on install (malicious versions 1.1.0, 1.2.0, 2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in unicore (PyPI)

MAL-2025-191916

Immediate action

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

pip uninstall unicore

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

5 flagged

1.1.01.2.022.0.02.0.1

Indicators of compromise (SHA-256)

ca27ad347572f42104429b5ac825cc6b34013e9160cc83df29e03d7278f58d13

d0c63e3dde8ac739b216a37381f04cd29e543075af8fb347b1685daf4a84e9d6

6961d9038d4217ddc5d24b394cb33095881de5c013594fc778dcf7ed430f651f

1318b378c8527c9b7c94c87fe927e87bf7e2140f4eb9b962bb08b4e1405ab624

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for unicore (5 malicious versions).
If you installed it — respond
Remove unicore 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 unicore 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. unicore on PyPI has been identified as a malicious package (versions 1.1.0, 1.2.0, 2, 2.0.0, 2.0.1 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 unicore-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