Which versions of apkeep are malicious?

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

How do I remediate apkeep if I installed it?

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

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

Yes — apkeep is associated with the 2026-05-apkeep 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 apkeep 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 apkeep (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging apkeep across your stack and pipelines.

Malicious package

apkeepPyPI

Malicious code in apkeep (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-3431

Immediate action

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

pip uninstall apkeep

What this malware does

The package pretends to be a fork of a legitimate Rust library and uses the identity of the original authors. During usage, the obfuscated code targets information held by Kanji/Iru security tools and exfiltrates basic informations to typosquated domain.

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

Campaign: 2026-05-apkeep

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.
obfuscation
impersonation
action-hidden-in-lib-usage

Malicious versions

2 flagged

0.1.01.0.1

Indicators of compromise (SHA-256)

d545ff7c3c178485cfb49d0028c4c808e67d0ee0fddcb4b7b195c943bb07d888

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 apkeep (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging apkeep across your stack and pipelines.
If you installed it — respond
apkeep 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 apkeep 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 apkeep 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. apkeep on PyPI has been identified as a malicious package (versions 0.1.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-05-apkeep

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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