request-cache-py is a malicious PyPI package that impersonates the popular requests-cache library. On import, it executes code that reads private keys and credentials from common developer secret locations (e.g., ~/.ssh/, ~/.aws/, ~/.gitconfig), extracts browser login data, cookies, and history from Chrome, Edge, and Safari SQLite databases, and collects environment variables containing sensitive keywords. The stolen data is exfiltrated via a Telegram bot webhook with the bot token and chat ID obfuscated using base64 splitting. The package includes sandbox evasion to avoid execution in CI or containerized environments and suppresses repeated exfiltration within 24 hours using a local marker file. This malicious code is embedded directly in the package, making it a supply-chain threat targeting human developers.

Successful import of this package leads to the theft of a wide range of sensitive credentials and secrets from the developer's environment, including SSH private keys, cloud credentials, Git credentials, npm and Docker configuration files, browser saved logins and cookies, and environment variables containing secrets. This can result in unauthorized access to source code repositories, cloud resources, developer accounts, and other sensitive systems. The exfiltration to a Telegram bot provides attackers with direct access to stolen secrets, enabling further compromise. The sandbox evasion reduces the chance of detection during automated analysis, increasing the risk of prolonged undetected compromise.

No official patch or remediation is indicated in the provided data. Users should immediately stop using the request-cache-py package and remove it from their environments. Verify that no sensitive credentials have been compromised and rotate any potentially exposed secrets, including SSH keys, cloud credentials, and API tokens. Use only verified and trusted packages from official sources, and consider implementing supply-chain security measures such as package signing and dependency auditing. Monitor for any suspicious activity related to exposed credentials. Patch status is not yet confirmed — check the vendor advisory or PyPI security advisories for current remediation guidance.