Which versions of requests-toolkit are malicious?

The following PyPI versions of requests-toolkit are flagged malicious: 0.1.2, 0.1.3. Treat any of these as compromised.

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

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

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

Yes — requests-toolkit is associated with the 2026-02-requests-toolkit 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 requests-toolkit across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for requests-toolkit (2 malicious versions).

Malicious package

requests-toolkitPyPI

Advisory published Feb 15, 2026Updated Feb 15, 2026

requests-toolkit is a confirmed malicious PyPI package (MAL-2026-903) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.2, 0.1.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in requests-toolkit (PyPI)

MAL-2026-903

Immediate action

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

pip uninstall requests-toolkit

What this malware does

During import, package masquerade and starts an embedded executable. The executable has signs of infostealer activity

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-02-requests-toolkit

Reasons (based on the campaign):

impersonation
infostealer
malware
The package contains code to detect if it is running in a sandbox environment.
keylogger

Malicious versions

2 flagged

0.1.20.1.3

Indicators of compromise (SHA-256)

ccf88804317b4caf9661eb94c320a521f7689c5cf26a8754ec219d268fc9c873

Detection & response playbook

Credential / info stealer

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

Campaign

2026-02-requests-toolkit

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database