Which versions of vtranalytic are malicious?

The following PyPI versions of vtranalytic are flagged malicious: 9.0.1. 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 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 (version 9.0.1). 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 version 9.0.1). 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

Package implements a Telegram-bot-driven remote administration tool that gives whoever holds the configured bot token full control of the installer's host. A polling loop calls the Telegram getUpdates API and dispatches received messages as shell commands through subprocess.run (SystemAnalyzer.execute_analysis), exposing a documented run command to execute arbitrary system commands. Additional handlers (findbot/getallbots) walk the filesystem (/, /home, /root, /etc, /var/www, /opt, /usr/local, /tmp, Windows drive roots and user profile directories), read.py/.json/.conf/.cfg/.env/.ini files, and regex-extract third-party Telegram bot tokens (BOT_TOKEN, API_TOKEN, TELEGRAM_TOKEN, [0-9]+:[A-Za-z0-9_-]+), returning them to the remote operator. File and credential exfiltration handlers (getfile, getdir, findget, getsystem, getconfig, getpasswords, getsshkeys, rdpall) read arbitrary installer paths — including SSH keys and stored credentials — and upload them to the operator's Telegram chat via requests.post to api.telegram.org sendDocument. The package advertises itself as a 'Complete VPS Control System' with 168+ admin commands including user creation and firewall modification.

Malicious versions

1 flagged

9.0.1

Indicators of compromise (SHA-256)

ebce016051a9e9cb604067185042ce49c7426aa1ac01aa606e430c4d1120eec7

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 (version 9.0.1). 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 (version 9.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010962

References

pypi.org

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