What does the rtcpstream 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 rtcpstream are malicious?

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

How do I remediate rtcpstream if I installed it?

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

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

Yes — rtcpstream is associated with the 2025-11-mescouilles, RLMA-2025-06589, RLUA-2026-00734 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 rtcpstream 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 rtcpstream (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 rtcpstream across your stack and pipelines.

Malicious package

rtcpstreamPyPI

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

MAL-2025-191859

Immediate action

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

pip uninstall rtcpstream

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)

76fd23fd0083cd92f54a3f978af8e6e1b8aa95d236da2328cf5a260239c5def7

aa2920b4ae77a6e47bbf9ac8163f8d9a30d62966097d34989a36103a76178558

89bd7d9fa95f2494111812f01e75537ad3d14a7856408d27793f1e05d410253d

be273d0fb5c34d1f77a1cad2785f1d4cc37170d7b4a888c735c7d8eedc7b4544

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 rtcpstream (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 rtcpstream across your stack and pipelines.
If you installed it — respond
rtcpstream 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 rtcpstream 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 rtcpstream 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. rtcpstream 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-06589RLUA-2026-00734

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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