Which versions of readosso are malicious?

The following PyPI versions of readosso are flagged malicious: 0.1.0, 0.1.2, 0.1.3. Treat any of these as compromised.

How do I remediate readosso if I installed it?

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

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

Yes — readosso is associated with the 2025-09-readosso 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 readosso across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for readosso (3 malicious versions).

Malicious package

readossoPyPI

Advisory published Sep 20, 2025Updated Dec 31, 2025

readosso is a confirmed malicious PyPI package (MAL-2025-191852) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.2, 0.1.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in readosso (PyPI)

MAL-2025-191852

Immediate action

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

pip uninstall readosso

What this malware does

Package automatically starts a Discord bot waiting for instructions to download and start a remote executable

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

Campaign: 2025-09-readosso

Reasons (based on the campaign):

Downloads and executes a remote executable.

Malicious versions

3 flagged

0.1.00.1.20.1.3

Indicators of compromise (SHA-256)

1356b92d6f2c7d60d9cfece6ea97d05e7e9cd006d99a6f2eadf7b62844f42091

67ade73536cb4834ba05b33797c1cadcddbf7d90fc099bd6e53f94b9deec4f66

74cd4ff5c32f6a9b4b0ddfef77eccc52176a567e653ea7e6e3afa72a2bf33343

Detection & response playbook

Credential / info stealer

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

Campaign

2025-09-readosso

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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