Which versions of manik are malicious?

The following PyPI versions of manik are flagged malicious: 1.2.1. Treat any of these as compromised.

How do I remediate manik if I installed it?

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

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

Yes — manik is associated with the 2026-07-manik 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 manik across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for manik (version 1.2.1).

Malicious package

manikPyPI

Advisory published Jul 8, 2026Updated Jul 8, 2026

manik is a confirmed malicious PyPI package (MAL-2026-7006) that steals credentials and exfiltrates sensitive data (malicious version 1.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in manik (PyPI)

MAL-2026-7006

Immediate action

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

pip uninstall manik

What this malware does

During installation, the package exfiltrates random files.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-07-manik

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
files-exfiltration

Malicious versions

1 flagged

1.2.1

Indicators of compromise (SHA-256)

9f5401ff0b4189038b0682df9360adf8a7b3f1c0b19f41726a9bb1ebb6770d5e

Detection & response playbook

Credential / info stealer

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

Campaign

2026-07-manik

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

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