Which versions of ritch are malicious?

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

How do I remediate ritch if I installed it?

ritch is a typosquat — you almost certainly intended a legitimately-named package. Remove ritch, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

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

Yes — ritch is associated with the GENERIC-local-typosquatting 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 ritch 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 ritch (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 ritch across your stack and pipelines.

Malicious package

ritchPyPI

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

MAL-2026-869

Immediate action

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

pip uninstall ritch

What this malware does

Package is a typosquatting or dependency confusion attempt with a low-harm local-only action, like leaving a flag file.

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-local-typosquatting

Reasons (based on the campaign):

dependency-confusion
The package overrides the install command in setup.py to execute malicious code during installation.
typosquatting

The OpenSSF Package Analysis project identified 'ritch' @ 1.0.0 (pypi) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

bc0d5c6c0c3175de2d5def02fe422574cfee5f7fe3a88f894de7122aa9dcf588

53836e778fae351105bebc4ec62937db1766d236b1ab050c142e8a57d863c7ea

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ritch (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 ritch across your stack and pipelines.
If you installed it — respond
ritch is a typosquat — you almost certainly intended a legitimately-named package. Remove ritch, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If ritch 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 ritch 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. ritch 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

GENERIC-local-typosquatting

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter
OpenSSF: Package Analysis · finder

Detect & block this

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