Which versions of reqeustx are malicious?

The following PyPI versions of reqeustx are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate reqeustx if I installed it?

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

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

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

Malicious package

reqeustxPyPI

reqeustx is a confirmed malicious PyPI package (MAL-2024-5866) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in reqeustx (PyPI)

MAL-2024-5866

Immediate action

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

pip uninstall reqeustx

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

40ee3aed138eaca4c66a5e45af3122eb5b19ed0e25a99e06ccda88211fdfa5e0

cecbbc0bed9247b02f04ff0eb7f7cc8f148c0950c2959d2378c3826666da41a3

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for reqeustx (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging reqeustx across your stack and pipelines.
If you installed it — respond
Remove reqeustx 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 reqeustx 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 reqeustx 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. reqeustx on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-04667RLUA-2024-09126

References

Credits

ReversingLabs · finder

Detect & block this

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