Which versions of darkig are malicious?

The following PyPI versions of darkig are flagged malicious: 1.0, 2.0. Treat any of these as compromised.

How do I remediate darkig if I installed it?

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

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

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

Search your lockfiles and build artifacts for darkig (2 malicious versions).

Malicious package

darkigPyPI

Advisory published Mar 13, 2026Updated Mar 14, 2026

darkig is a confirmed malicious PyPI package (MAL-2026-1409) that steals credentials and exfiltrates sensitive data (malicious versions 1.0, 2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in darkig (PyPI)

MAL-2026-1409

Immediate action

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

pip uninstall darkig

What this malware does

Instagram hacking tool that also forces the user 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

2 flagged

1.02.0

Indicators of compromise (SHA-256)

7589c67c4429eabd010f891cb17f893ee11ec3cb873d4a31095cc3592134f762

Detection & response playbook

Credential / info stealer

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