Which versions of ransomware are malicious?

The following PyPI versions of ransomware are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate ransomware if I installed it?

ransomware carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.

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

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

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

Malicious package

ransomwarePyPI

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

MAL-2025-1988

Immediate action

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

pip uninstall ransomware

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

3a0588fb5593464ad7203344644a0e171f285ddfca658dd4d39cf29858df2827

Detection & response playbook

Destructive / sabotage

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ransomware (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ransomware across your stack and pipelines.
If you installed it — respond
ransomware carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.
Did it already run?
If ransomware 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 ransomware 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. ransomware on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-01231

Credits

ReversingLabs · finder

Detect & block this

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

ransomwarePyPI

Malicious versions

Indicators of compromise (SHA-256)

Detection & response playbook

Find it

If you installed it — respond

Did it already run?

How O3 protects you

Frequently asked questions

Campaign

Credits

Detect & block this