Which versions of modernreqs are malicious?

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

How do I remediate modernreqs if I installed it?

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

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

Yes — modernreqs is associated with the RLMA-2024-08528, 2024-08-invokehttp, RLUA-2026-00532 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 modernreqs 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 modernreqs (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 modernreqs across your stack and pipelines.

Malicious package

modernreqsPyPI

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

MAL-2024-10048

Immediate action

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

pip uninstall modernreqs

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)

257f4254a0e701b5dd154caab8125fdcfa160a8708d2ff6e4dd9cd53a64f38e2

57c35ce4651c1abf936517a1becf0630d15f648e2ce6b0a4c574e07a27b7eebc

39c894cc5c48e2c1485dce3f861ccf0b768aeafeddf6e865ec8ef8db7b1407a0

7dd7da7a154f0db10229acd8492fea450f0d0d7414693d653e880a9ed0894907

999ac2095a7d554f4f2cdac5dfebb506a7d4d7b7fa99de5c7bef6abc281f5241

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 modernreqs (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 modernreqs across your stack and pipelines.
If you installed it — respond
modernreqs 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 modernreqs 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 modernreqs 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. modernreqs 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-085282024-08-invokehttpRLUA-2026-00532

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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