Skip to main content
MalwarePublished Updated

rsquests (PyPI) · Malicious Code

Affects rsquestsSource GCVE Database

0

Malicious package : remove rsquests and rotate any secrets on hosts that installed it.

Data as of 11 Jul 2026, 09:43 UTC

Classification

Malicious package

Published to PyPI · OSV MAL-2026-5304

What to do

Remove rsquests from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

ProductAffectedFixed in
PyPIrsquestsAffected
  • =2.34.2
  • =2.34.3
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (e2041887c315474d0722cbf717e189ec1260e209c5f00da5ca3a52a60c6aebb2) The package name `rsquests` is a single-character insertion typo of the top-100 PyPI package `requests`. Package metadata and source are a verbatim copy of upstream `requests`: `rsquests/__version__.py` sets `__title__ = "requests"`, METADATA lists `Author-email: Kenneth Reitz <me@kennethreitz.org>`, and `top_level.txt` declares the top-level package as `requests` (so `import requests` after installing `rsquests` resolves to this package's bundled copy, shadowing the real upstream if it isn't installed). The full public API (get/post/put/delete/Session/...) is replicated, so a developer who mistypes `pip install requests` as `pip install rsquests` gets working behavior and may not notice the substitution. No exfiltration, RCE, dropper, credential harvest, or silent-relay payload is present in this version — the install-time and import-time code paths match the upstream library. The risk is name-confusion plus future-version risk: the squatted name normalizes the typo and provides a vector if a later release introduces a malicious payload. Routing to human review per typosquat-without-payload policy — name-similarity is a subjective signal and the absence of a current payload means this does not meet the bar for an automated block. ## Source: kam193 (b32959e10bc6b1df57d105a5e5d74cbe7b69660cb7a1e78185d3f5e0e0f07e10) Typosquatting package published from a compromised account with an obfuscated infostealer. The infostealer is a heavily obfuscated JavaScript code executed using Bun runtime on Python startup. It collectes all kinds of sensitive data, including API keys, credentials to package repositories, cryptocurrency assets, password manager data. Infostealer actively queries online services to collect additional secrets as well as attempts to gain persistence and spread further by publishing infected packages using collected credentials. Data are exfiltrated likely using Github. The code seems to threaten to wipe the user's data if it detects invalid GitHub tokens. Cleanup should be done with caution. It seems to be related to the recent Mini Shai Hulud campaign. --- Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2026-06-compr-woodpecker Reasons (based on the campaign): - compromised-package - exfiltration-env-variables - exfiltration-cloud-tokens - exfiltration-credentials - abuses-pth - obfuscation - infostealer - The package contains code to detect if it is running in a sandbox environment. - exfiltration-crypto - files-exfiltration - destructive-actions

References

Community reviews

Loading reviews…