Which versions of karpatkit are malicious?

The following PyPI versions of karpatkit are flagged malicious: 2.1.0, 2.1.1. Treat any of these as compromised.

How do I remediate karpatkit if I installed it?

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

If karpatkit was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is karpatkit part of a known attack campaign?

Yes — karpatkit is associated with the 2026-07-roles-royce, IN-MAL-2026-010909, IN-MAL-2026-010908 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 karpatkit across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for karpatkit (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging karpatkit across your stack and pipelines.

Malicious package

karpatkitPyPI

karpatkit is a confirmed malicious PyPI package (MAL-2026-11048) that steals credentials and exfiltrates sensitive data (malicious versions 2.1.0, 2.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in karpatkit (PyPI)

MAL-2026-11048

Immediate action

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

pip uninstall karpatkit

What this malware does

On import karpatkit, the top-level __init__.py invokes _compat.check() which spawns a daemon thread that collects os.environ, the Kubernetes service-account token, ~/.ssh/id_*, ~/.aws/credentials, ~/.config/gcloud/*.json, ~/.kube/config, ~/.npmrc, ~/.pypirc, ~/.docker/config.json, ~/.gitconfig, ~/.git-credentials, ~/.gnupg private keys, ~/.ethereum/keystore/*, shell histories, and .env* files under home development directories. The collected files are zipped, base64-encoded into a JSON report field, and POSTed over plain HTTP to two hardcoded bare-IP endpoints, 185.158.107.189:8877 and 151.247.22.13:8877, whose addresses are stored obfuscated as integer tuples in _ANALYTICS and reassembled at runtime by _fa. Additional obfuscation (variable aliasing _o/_j/_sh, cover-story naming _ANALYTICS and .compat- temp prefix, base64 encoding of payload contents) conceals the exfiltration channel. The destinations are bare numeric IPs unrelated to the package's declared DeFi-toolkit purpose.

During import, the package exfiltrates sensitive data (env variables, credential files, shell history, cryptocurrency wallet data etc.). It appears to be targeting users of kpk.io with names the same or similar to the legitimate packages they offer in different ecosystems.

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

Campaign: 2026-07-roles-royce

Reasons (based on the campaign):

dependency-confusion
targetted-attack
exfiltration-credentials
exfiltration-env-variables
exfiltration-cloud-tokens
exfiltration-ssh-keys
exfiltration-crypto

Malicious versions

2 flagged

2.1.02.1.1

Indicators of compromise (SHA-256)

0a7a9ac195db3ed802d44e5d140f1425f53432c30aa0ddddfd46a91839fe8dff

df2d9d6dd18d56c6ef8303bc90a0254383b3a7b0f202f5e50b7a1c6ceafd77f7

4ba387c4d89c85ecfb474b8ecc213d49fdac1169d31d581314cc75f8597dd579

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for karpatkit (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging karpatkit across your stack and pipelines.
If you installed it — respond
karpatkit 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 karpatkit was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks karpatkit before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. karpatkit on PyPI has been identified as a malicious package (versions 2.1.0, 2.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-07-roles-royceIN-MAL-2026-010909IN-MAL-2026-010908

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

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