vtranalyticPyPI
Advisory published Updated
vtranalytic is a confirmed malicious PyPI package (MAL-2026-11156) that steals credentials and exfiltrates sensitive data (malicious versions 9.0.1, 9.0.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in vtranalytic (PyPI)
What this malware does
The package implements a full remote-administration toolkit controlled through a Telegram bot. It polls the Telegram Bot API at https://api.telegram.org/bot<token>/... and dispatches inbound messages to handlers that execute arbitrary system commands via subprocess.run (documented in the README as a run command that executes any system command), create OS users, change sudo/RDP privileges, and upload/download arbitrary files on the host. A BotFinder routine walks /, /home, /root, /etc, /var/www, /opt, /tmp, /usr/local, and Windows drives, reading.py/.json/.conf/.cfg/.env/.ini files and regex-extracting Telegram bot tokens (pattern [0-9]+:[A-Za-z0-9_-]+) along with token/api_token/webhook context. Additional bot commands (getpasswords, getsshkeys, rdp, rdpall, findbot, getallbots) return the harvested SSH keys, saved credentials, and other operators' bot tokens back over the Telegram channel. Any host on which this package runs is fully controllable by whoever holds the bot token, and installer-side secrets are exfiltrated to that operator. Package metadata lists a placeholder author (Umar <[email protected]>) and a non-existent GitHub slug, consistent with anonymous publication of a RAT under a data-analytics-sounding name.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for vtranalytic (2 malicious versions).
If you installed it — respond
vtranalytic 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 vtranalytic 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
Detect & block this
O3 blocks vtranalytic-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.