Which versions of upgrade-requests are malicious?

The following PyPI versions of upgrade-requests are flagged malicious: 3.0.0. Treat any of these as compromised.

How do I remediate upgrade-requests if I installed it?

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

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

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

Search your lockfiles and build artifacts for upgrade-requests (version 3.0.0).

Malicious package

upgrade-requestsPyPI

upgrade-requests is a confirmed malicious PyPI package (MAL-2025-41791) that executes malicious code on install (malicious version 3.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in upgrade-requests (PyPI)

MAL-2025-41791

Immediate action

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

pip uninstall upgrade-requests

Malicious versions

1 flagged

3.0.0

Indicators of compromise (SHA-256)

078e53992b0deb97209c3c58796a3d8cb6403ed69919a7e38ca964cfffd30af0

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-04289

Credits

ReversingLabs · finder

Detect & block this

O3 blocks upgrade-requests-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