Which versions of rcebymrx are malicious?

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

How do I remediate rcebymrx if I installed it?

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

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

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

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

Malicious package

rcebymrxPyPI

Advisory published Sep 23, 2024Updated Dec 12, 2025

rcebymrx is a confirmed malicious PyPI package (MAL-2024-8946) that steals credentials and exfiltrates sensitive data (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rcebymrx (PyPI)

MAL-2024-8946

Immediate action

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

pip uninstall rcebymrx

What this malware does

When importing the module, the /etc/passwd file is exfiltrated

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: 2024-09-mrx1w1

Reasons (based on the campaign):

files-exfiltration

The OpenSSF Package Analysis project identified 'rcebymrx' @ 0.0.1 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b40993e43a581dac0abf88febbde6e0fb833dffb80824ed65880847c3309968d

15f02f476bdb49f08203ae81feef2040d55d3b599ab38808c85ec5c3bbba6c63

65ddcbfb52d8c96bb51c713d62841675f75e9e5225efc9380917c6cf79bed8ab

4b29448a21fc4a8c94ef1cffba23cf91fdc28f419a3455f67f4963c2f29665d7

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for rcebymrx (version 0.0.1).
If you installed it — respond
rcebymrx 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 rcebymrx 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. rcebymrx 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

2024-09-mrx1w1

References

bad-packages.kam193.eu

Credits

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

Detect & block this

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