Which versions of curl-requester are malicious?

The following PyPI versions of curl-requester are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate curl-requester if I installed it?

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

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

Yes — curl-requester is associated with the RLMA-2026-00243 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 curl-requester across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for curl-requester (version 0.1.0).

Malicious package

curl-requesterPyPI

Advisory published Mar 18, 2026Updated Mar 19, 2026

curl-requester is a confirmed malicious PyPI package (MAL-2026-1898) that executes malicious code on install (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in curl-requester (PyPI)

MAL-2026-1898

Immediate action

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

pip uninstall curl-requester

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

aee52e609ebef33a72290e3de3d2d9b3859589cc2a374c3384170d72bc18c2b0

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for curl-requester (version 0.1.0).
If you installed it — respond
Remove curl-requester 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 curl-requester 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. curl-requester on PyPI has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-00243

Credits

ReversingLabs · finder

Detect & block this

O3 blocks curl-requester-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