Which versions of vtranalytic are malicious?

The following PyPI versions of vtranalytic are flagged malicious: 9.0.1, 9.0.4. Treat any of these as compromised.

How do I remediate vtranalytic if I installed it?

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.

I already installed vtranalytic — how do I know if it already compromised me?

If vtranalytic 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.

Is vtranalytic part of a known attack campaign?

Yes — vtranalytic is associated with the IN-MAL-2026-010962, IN-MAL-2026-014791 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find vtranalytic across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vtranalytic (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vtranalytic across your stack and pipelines.

Malicious package

vtranalyticPyPI

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)

MAL-2026-11156

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

pip uninstall vtranalytic

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

2 flagged

9.0.19.0.4

Indicators of compromise (SHA-256)

ebce016051a9e9cb604067185042ce49c7426aa1ac01aa606e430c4d1120eec7

897fa80f1d8a55ff480d6c7e7a71200ac31530a9f5d928389545b597c7b45903

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vtranalytic (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vtranalytic across your stack and pipelines.
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 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 vtranalytic 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

No. vtranalytic on PyPI has been identified as a malicious package (versions 9.0.1, 9.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010962IN-MAL-2026-014791

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database