Which versions of aiohttp-libscss are malicious?

The following PyPI versions of aiohttp-libscss are flagged malicious: 0.23.0, 0.23.1, 0.23.2, 0.24.0, 0.25.0, 0.26.0. Treat any of these as compromised.

How do I remediate aiohttp-libscss if I installed it?

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

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

Yes — aiohttp-libscss is associated with the RLMA-2024-07803, 2024-08-app-url-to-telegram, RLUA-2026-00042 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 aiohttp-libscss 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 aiohttp-libscss (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aiohttp-libscss across your stack and pipelines.

Malicious package

aiohttp-libscssPyPI

Malicious code in aiohttp-libscss (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-9937

Immediate action

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

pip uninstall aiohttp-libscss

What this malware does

Imitate legit package, when used, sends out the URL of web application using the package

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

Campaign: 2024-08-app-url-to-telegram

Reasons (based on the campaign):

clones-real-package
The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
dependency-confusion
action-hidden-in-lib-usage

Malicious versions

6 flagged

0.23.00.23.10.23.20.24.00.25.00.26.0

Indicators of compromise (SHA-256)

7e86db9cfebc3da4b6b1fe1fa23176f441477423b19eaf961cd04b88d675a8da

10e874787e38ecc45c41814fb6b05aa9b208d8834be111a799c02d007cf90d7f

d5cb2d30b1084d16cbffd08a377d8723d794f112d1d33e666a4d4154653015e0

51c95dddfe1fd8c1f56e3a0b9301e8b3bfb3c5feece0058e12a977dec2184d23

c4716ac05da16d0201292783458af845eba3b2ead25c15abbf7088ac99503ea5

b9873b94fea7b5b1954efb326f0da4ba979d184a281c04b37ccc3ece2f2f201a

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

Campaign

RLMA-2024-078032024-08-app-url-to-telegramRLUA-2026-00042

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks aiohttp-libscss-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