httpz-requestsPyPI
httpz-requests is a confirmed malicious PyPI package (MAL-2026-14130) that steals credentials and exfiltrates sensitive data (malicious versions 1.8.0, 1.9.0, 1.10.0…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in httpz-requests (PyPI)
What this malware does
httpz-requests exposes a Telegram bot (start_bot, run_cmd_enc, http_request) whose message handler executes arbitrary shell commands on the host running the package, granting a remote Telegram operator full command execution under the installer's user account. Documented remote commands include arbitrary shell execution (chalao, .sh <command>, .py <file>, .exec <file>), destructive filesystem operations (rm -rf <path>), single- and bulk-file exfiltration (take <file>, take all), a full-host backup mode that produces split 50MB archives with .partNNN chunking (get all), and environment-variable dumping (.printenv) — collectively enabling remote theft of filesystem contents and process-environment secrets (cloud, CI, and API credentials). The package is shipped only as compiled Cython .so files with no Python source, and self-describes obfuscation features that XOR+base64-encode command strings and disguise execution as http_request("POST",...) so plaintext commands do not appear in ps or system logs; the Telegram bot token is stored encoded and decoded at runtime by dec(). The distribution name httpz-requests and import name httpz_requests resemble the top-100 PyPI package requests while presenting a Telegram remote-shell API instead of an HTTP client, and metadata is unfilled boilerplate (author Aapka Naam <[email protected]>, homepage https://github.com/YOUR_GITHUB_USERNAME/httpz-requests).
The package provides Telegram-based remote access to the machine it runs on. It was deliberately created and used to hack other machines, exfiltrate files and credentials. This package automatically ensures persistence and starts a malicious process on import.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-08-httpz-requests
Reasons (based on the campaign):
-
files-exfiltration
-
rat
-
persistence
-
uses-telegram-bot
-
obfuscation
-
native-extension
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for httpz-requests (34 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging httpz-requests across your stack and pipelines.
If you installed it — respond
httpz-requests 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 httpz-requests was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks httpz-requests before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- Kamil Mańkowski (kam193) · reporter
Detect & block this
O3 blocks httpz-requests-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.