wacve-utilsPyPI
Advisory published Updated
wacve-utils is a confirmed malicious PyPI package (MAL-2026-11428) that steals credentials and exfiltrates sensitive data (malicious version 1.0.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in wacve-utils (PyPI)
What this malware does
On import wacve_utils, the package's __init__.py unconditionally invokes check_for_updates(), which HTTP-fetches a hardcoded GitHub Gist under the user Darknet-Hacker (gist.githubusercontent.com/Darknet-Hacker/7f7e01a86e68403a457c4cd0c2d93f1d/raw/), base64-decodes the body, XORs it with a key derived from the string wacve_utils, zlib-decompresses it, marshal.loads a Python code object, and execs it in-process. If the Gist fetch fails, the module falls back to shipped opaque blobs config-linux.dat / config-termux.dat (selected by a Termux/Linux platform branch) and runs them through the same base64+XOR+zlib+marshal decode-and-exec path. No pinning, no signature verification, and the payload is mutable by the Gist owner. The package advertises itself as Lightweight utilities for chat application security checks and exposes a stub check_vulnerability that returns a random boolean — a cover story unrelated to the executed payload. Importing this package grants the Gist owner arbitrary code execution in the installer's Python process.
The package contains encrypted code with infostealers targeting Linux and Android (execution under Termux). The encrypted code collects files, browsers data, text messages and exfiltrates them to a Telegram channel.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-08-wacve-utils
Reasons (based on the campaign):
-
files-exfiltration
-
exfiltration-browser-data
-
uses-telegram-bot
-
obfuscation
-
Downloads and executes a remote malicious script.
-
infostealer
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for wacve-utils (version 1.0.7).
If you installed it — respond
wacve-utils 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 wacve-utils 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
Campaign
References
Credits
- Amazon Inspector · finder
- Kamil Mańkowski (kam193) · reporter
Detect & block this
O3 blocks wacve-utils-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.