Which versions of hangimani are malicious?

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

How do I remediate hangimani if I installed it?

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

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

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

Search your lockfiles and build artifacts for hangimani (version 1.0.0).

Malicious package

hangimaniPyPI

Advisory published Feb 2, 2026Updated Feb 23, 2026

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

Malicious code in hangimani (PyPI)

MAL-2026-625

Immediate action

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

pip uninstall hangimani

What this malware does

During importing the module, package downloads a second-stage code from GitHub, which then runs an infostealer. After that, the downloaded code is removed

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

Campaign: 2026-02-old-hangman

Reasons (based on the campaign):

Downloads and executes a remote malicious script.
infostealer
covering-tracks

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

4eb1b67eac28a42f372ecaaca274a28d15972e3cc8e063492f977364538e6c41

d0bfb239431bc716583843c5ca362ba4df71ff1beaed771ec95e3dcad22753a2

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for hangimani (version 1.0.0).
If you installed it — respond
hangimani 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 hangimani 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. hangimani 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

2026-02-old-hangman

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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