Which versions of hackling are malicious?

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

How do I remediate hackling if I installed it?

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

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

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

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

Malicious package

hacklingPyPI

Advisory published May 13, 2026Updated May 13, 2026

hackling is a confirmed malicious PyPI package (MAL-2026-3665) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hackling (PyPI)

MAL-2026-3665

Immediate action

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

pip uninstall hackling

What this malware does

Package automatically exfiltrate information about the system, including potentially sensitive data.

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

Campaign: 2026-05-hackling

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
exfiltration-env-variables

Malicious versions

2 flagged

1.0.01.0.2

Indicators of compromise (SHA-256)

cf12b321da2b42ce2302bdccbb35304c4f4a47c7a5e273076467b269982c480f

Detection & response playbook

Credential / info stealer

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

Campaign

2026-05-hackling

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

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