Which versions of ighack are malicious?

The following PyPI versions of ighack are flagged malicious: 3.0. Treat any of these as compromised.

How do I remediate ighack if I installed it?

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

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

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

Search your lockfiles and build artifacts for ighack (version 3.0).

Malicious package

ighackPyPI

Advisory published Mar 13, 2026Updated Mar 14, 2026

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

Malicious code in ighack (PyPI)

MAL-2026-1410

Immediate action

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

pip uninstall ighack

What this malware does

Instagram hacking tool that besides abusing the Instagram API, also automatically uses user's credentials to follow hardcoded accounts.

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

Campaign: 2026-03-old-nai

Reasons (based on the campaign):

exfiltration-credentials
abusing-3rd-api
action-hidden-in-lib-usage

Malicious versions

1 flagged

3.0

Indicators of compromise (SHA-256)

889207a729f6b97c385d6c0afe217776d10331cdf7e5dd511f80e0d01e899842

Detection & response playbook

Credential / info stealer

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

Campaign

2026-03-old-nai

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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