Which versions of keybard are malicious?

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

How do I remediate keybard if I installed it?

Remove keybard from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed keybard — how do I know if it already compromised me?

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

Yes — keybard is associated with the RLMA-2025-02576, RLUA-2025-03626 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 keybard across my projects, lockfiles, and CI pipelines?

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

Malicious package

keybardPyPI

keybard is a confirmed malicious PyPI package (MAL-2025-4221) that executes malicious code on install (malicious versions 0.1.0, 0.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in keybard (PyPI)

MAL-2025-4221

Immediate action

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

pip uninstall keybard

Malicious versions

2 flagged

0.1.00.2.0

Indicators of compromise (SHA-256)

7da040834c0d65c1e8050a9b4363333d846b7684f0a411ad3a5aec25f2221f25

02b8a5f4307539bec0fbcc14b637aa16de7c238647ed0fab1867ded1c5c0457c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for keybard (2 malicious versions).
If you installed it — respond
Remove keybard from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If keybard 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. keybard on PyPI has been identified as a malicious package (versions 0.1.0, 0.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-02576RLUA-2025-03626

Credits

ReversingLabs · finder

Detect & block this

O3 blocks keybard-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database