Which versions of asyncmodules are malicious?

The following PyPI versions of asyncmodules are flagged malicious: 2.3.5. Treat any of these as compromised.

How do I remediate asyncmodules if I installed it?

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

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

Yes — asyncmodules is associated with the RLMA-2024-10977, 2024-08-invokehttp, RLUA-2026-00091 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 asyncmodules 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 asyncmodules (version 2.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging asyncmodules across your stack and pipelines.

Malicious package

asyncmodulesPyPI

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

MAL-2024-11533

Immediate action

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

pip uninstall asyncmodules

What this malware does

In the invokehttp, the init.py contains obfuscated code attempting to download and run one of two executables. They are identified as malicious by VT and the tracks of Telegram URLs suggests attempting data exfiltration. The package itself looks like a copy of requests. In flophttp, using exactly the same obfuscation method, the infostealer is directly embeded into package code and exfiltrates data to a telegram channel.

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

Campaign: 2024-08-invokehttp

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.
obfuscation
clones-real-package

Malicious versions

1 flagged

2.3.5

Indicators of compromise (SHA-256)

b2c1183899f718bc785b55c78cfac2b90945b16a7a16af8cd74677a89484dfd3

f584355fc4dd04444c8436f9e8458c3112198801fd43940322942c3005c7d255

4089e0f824ae366e1e3e128e2213a6700d6bddea0b9209fd426148a0792edd53

249cd96039a8f96f9bc8cb3a16afb5018ab0bf82cc769fcb02de8decc7a89bc8

b23c4b7bcffa6ce87e0442939063b4cd987455a2670617876eb6e4c5192e8a5f

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

Campaign

RLMA-2024-109772024-08-invokehttpRLUA-2026-00091

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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