Which versions of indpack are malicious?

The following PyPI versions of indpack are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate indpack if I installed it?

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

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

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

Search your lockfiles and build artifacts for indpack (version 0.1.0).

Malicious package

indpackPyPI

Advisory published Mar 20, 2026Updated Mar 23, 2026

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

Malicious code in indpack (PyPI)

MAL-2026-2114

Immediate action

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

pip uninstall indpack

What this malware does

These packages are used as build dependencies of malicious packages in newer waves of the campaign 2026-02-urllib-slim. They are used to split the malicious action between dependencies and are not malicious alone, but are used together to: exfiltrate information through DNS, collect information about the processes and covering tracks by installing packages from local private repositories.

Package nspack additionally notifies upon importing a domain known for malicious activity with the package and hostname.

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

Campaign: 2026-03-geekennedy

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.
The malicious code is intentionally included in a dependency of the package

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

85f1ca1d5abdcf2139039fc5e8a08068a8c2cacca8a31fed38fbde74f7b8c04d

Detection & response playbook

Credential / info stealer

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

Campaign

2026-03-geekennedy

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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