Which versions of reqest-dexfree are malicious?

The following PyPI versions of reqest-dexfree are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate reqest-dexfree if I installed it?

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

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

Yes — reqest-dexfree is associated with the RLMA-2025-00508 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 reqest-dexfree across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for reqest-dexfree (version 0.0.1).

Malicious package

reqest-dexfreePyPI

reqest-dexfree is a confirmed malicious PyPI package (MAL-2025-967) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in reqest-dexfree (PyPI)

MAL-2025-967

Immediate action

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

pip uninstall reqest-dexfree

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

88b55ed042f25308666591c3b45d57c8d392946c92d4c56fe542d3f7458a2dd7

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-00508

Credits

ReversingLabs · finder

Detect & block this

O3 blocks reqest-dexfree-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