Which versions of karpatkey are malicious?

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

How do I remediate karpatkey if I installed it?

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

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

Yes — karpatkey is associated with the 2026-07-roles-royce, IN-MAL-2026-010937 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 karpatkey 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 karpatkey (version 2.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging karpatkey across your stack and pipelines.

Malicious package

karpatkeyPyPI

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

Malicious code in karpatkey (PyPI)

MAL-2026-11047

Immediate action

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

pip uninstall karpatkey

What this malware does

On import karpatkey, the top-level karpatkey/__init__.py spawns a daemon background thread that walks the installer's home directory and collects SSH private keys (~/.ssh/id_*), AWS credentials (~/.aws/credentials), GCP credentials (~/.config/gcloud/), kubeconfig (~/.kube/config), Ethereum wallet keystores (~/.ethereum/keystore/*), GnuPG private keys (~/.gnupg/private-keys-v1.d/*), .npmrc/.pypirc/docker/git credentials, shell histories, .env* files under Desktop/Projects/repos/code/src/work, Kubernetes service-account tokens from /var/run/secrets/kubernetes.io/serviceaccount, and the full os.environ. The archive is zipped, base64-encoded and POSTed via plain HTTP to two hardcoded bare-IP destinations, 185.158.107.189:8877 and 151.247.22.13:8877, encoded as integer tuples in an _ANALYTICS list and reassembled at runtime by an _fa helper. The module karpatkey/_compat.py presents itself as a "Runtime environment compatibility layer" and stages the archive as .compat_cache.zip, a cover-story that does not match the observed behavior. The destinations are unrelated to the declared publisher domain kpk.io.

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

1 flagged

2.1.1

Indicators of compromise (SHA-256)

ea7a30728a3c4f46fee3153895404941b4363cb7086f5efe55e9ae9931913395

b434ae7cf6afb9ce18a54757c03069983e404db695d959bd29aa628864b8349c

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 karpatkey (version 2.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging karpatkey across your stack and pipelines.
If you installed it — respond
karpatkey 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 karpatkey 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 karpatkey 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. karpatkey on PyPI has been identified as a malicious package (version 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-010937

References

Credits

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

Detect & block this

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