Which versions of aiohttp-proxies-forked are malicious?

The following PyPI versions of aiohttp-proxies-forked are flagged malicious: 0.1.65. Treat any of these as compromised.

How do I remediate aiohttp-proxies-forked if I installed it?

Remove aiohttp-proxies-forked from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed aiohttp-proxies-forked — how do I know if it already compromised me?

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

Yes — aiohttp-proxies-forked is associated with the RLMA-2025-04109 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-proxies-forked across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for aiohttp-proxies-forked (version 0.1.65).

Malicious package

aiohttp-proxies-forkedPyPI

aiohttp-proxies-forked is a confirmed malicious PyPI package (MAL-2025-41618) that executes malicious code on install (malicious version 0.1.65). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aiohttp-proxies-forked (PyPI)

MAL-2025-41618

Immediate action

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

pip uninstall aiohttp-proxies-forked

Malicious versions

1 flagged

0.1.65

Indicators of compromise (SHA-256)

eec2ed15af2aa353c0a36d7ccc9dbe2eef881bca7e38835197b40542de479e51

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for aiohttp-proxies-forked (version 0.1.65).
If you installed it — respond
Remove aiohttp-proxies-forked from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If aiohttp-proxies-forked 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. aiohttp-proxies-forked on PyPI has been identified as a malicious package (version 0.1.65 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04109

Credits

ReversingLabs · finder

Detect & block this

O3 blocks aiohttp-proxies-forked-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database