Which versions of pysigner are malicious?

The following PyPI versions of pysigner are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate pysigner if I installed it?

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

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

Yes — pysigner is associated with the RLMA-2024-08998 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 pysigner across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pysigner (version 0.0.1).

Malicious package

pysignerPyPI

pysigner is a confirmed malicious PyPI package (MAL-2024-10121) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pysigner (PyPI)

MAL-2024-10121

Immediate action

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

pip uninstall pysigner

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f3a27ed5dbc8ebbca596fc030e23652eba69ebdbf11c79376539d3e8d1fd301e

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-08998

Credits

ReversingLabs · finder

Detect & block this

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