What does the rtcpy malware do?

Importing the module starts an infostealer Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2025-11-mescouilles Reasons (based on the campaign): - infostealer - infostealer:kiwi - infostealer:cstealer - exfiltration-generic - exfiltration-browser-data - exfiltration-credentials - files-exfiltration - The package contains code to detect if it is running in a sandbox environment.

Which versions of rtcpy are malicious?

The following PyPI versions of rtcpy are flagged malicious: 1.6.3. Treat any of these as compromised.

How do I remediate rtcpy if I installed it?

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

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

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

Malicious package

rtcpyPyPI

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

MAL-2025-191860

Immediate action

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

pip uninstall rtcpy

What this malware does

Importing the module starts an infostealer

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

Campaign: 2025-11-mescouilles

Reasons (based on the campaign):

infostealer
infostealer:kiwi
infostealer:cstealer
exfiltration-generic
exfiltration-browser-data
exfiltration-credentials
files-exfiltration
The package contains code to detect if it is running in a sandbox environment.

Malicious versions

1 flagged

1.6.3

Indicators of compromise (SHA-256)

d53ecaa63619cf23476b4b92f14735f3256c4100ed0ba7e23faa8415a96bf7fd

75bd7b21b8b27920b63ff14b07b761f57e72da9866682e4e49bd569e660215fd

c601d4a5e29121beb4fc9b5fb6c4506b51f974348400bfba49319863ad1d2364

78416faf9ec6de7f77ca85b65e50c3f5277a68e50bf53775bc8430533a430f5c

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 rtcpy (version 1.6.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rtcpy across your stack and pipelines.
If you installed it — respond
rtcpy 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 rtcpy 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 rtcpy 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. rtcpy on PyPI has been identified as a malicious package (version 1.6.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-11-mescouillesRLMA-2025-06590RLUA-2026-00735

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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