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

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

How do I remediate aiostreams if I installed it?

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

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

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

Malicious package

aiostreamsPyPI

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

MAL-2025-191675

Immediate action

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

pip uninstall aiostreams

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

0.0.1

Indicators of compromise (SHA-256)

e998d7ff65c4a84a2a570510eac3f440b97f22877312abeb234803babaf8fd20

a6bc4c2d12a8ad24e8844bea0287de82e1e6ab24b08fb1f5ac983c0906a655d9

cb88717713d2cfea9c802c72e9939fd55a3d3ae6db8a8f8ae88c9f0377a73335

b6fd3158674e546ccd09121f039317c167a1adae62404b9fe99760f0c252adca

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 aiostreams (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aiostreams across your stack and pipelines.
If you installed it — respond
aiostreams 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 aiostreams 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 aiostreams 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. aiostreams 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

2025-11-mescouillesRLMA-2025-06550RLUA-2026-00048

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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