Which versions of python-ledgercommon are malicious?

The following PyPI versions of python-ledgercommon are flagged malicious: 1.56.2, 1.56.3, 1.56.4, 1.56.5, 1.56.6, 1.56.7, 1.56.8, 1.56.9, 1.56.10, 1.56.11, 1.56.12, 1.56.13, 1.56.14, 2.3.1, 2.3.2. Treat any of these as compromised.

How do I remediate python-ledgercommon if I installed it?

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

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

Yes — python-ledgercommon is associated with the RLMA-2025-04806, GENERIC-standard-pypi-install-pentest, RLUA-2026-00666 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 python-ledgercommon 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 python-ledgercommon (15 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging python-ledgercommon across your stack and pipelines.

Malicious package

python-ledgercommonPyPI

Malicious code in python-ledgercommon (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-47799

Immediate action

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

pip uninstall python-ledgercommon

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

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.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

15 flagged

1.56.21.56.31.56.41.56.51.56.61.56.71.56.81.56.91.56.101.56.111.56.121.56.131.56.142.3.12.3.2

Indicators of compromise (SHA-256)

ad179bc1a377cd06297c2e2f2115dc46be47eabf42f8342371c0435b433dec2f

bfb38b2ba9b265c2e4f55f4dfedef3b1796af3ed8ec121672e1aa34c369a9a82

d88522028116659a8646b0f7c4eb4e6218e498b49ebc36927ca0787720d3e1f9

b44aea47181f52536bf2b5a7ef34b9b494e89e404456153f14c0b39e056628ad

ca4ab49e6361702d27570a16cfd1e3e63e27c64036364c8e6dc4201c71909b29

6f63e34bdc5d64cc13c651615ac70a1c0e491dd52de75f50fefa97449b1242ea

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 python-ledgercommon (15 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging python-ledgercommon across your stack and pipelines.
If you installed it — respond
python-ledgercommon 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 python-ledgercommon 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 python-ledgercommon 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. python-ledgercommon on PyPI has been identified as a malicious package (versions 1.56.2, 1.56.3, 1.56.4, 1.56.5, 1.56.6, 1.56.7, 1.56.8, 1.56.9, and 7 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04806GENERIC-standard-pypi-install-pentestRLUA-2026-00666

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks python-ledgercommon-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