Which versions of torchvisions are malicious?

The following PyPI versions of torchvisions are flagged malicious: 94.6. Treat any of these as compromised.

How do I remediate torchvisions if I installed it?

torchvisions 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 torchvisions — how do I know if it already compromised me?

If torchvisions 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 torchvisions part of a known attack campaign?

Yes — torchvisions is associated with the RLMA-2024-11190, 2024-11-byted-dast, RLUA-2026-00831 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 torchvisions 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 torchvisions (version 94.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging torchvisions across your stack and pipelines.

Malicious package

torchvisionsPyPI

Malicious code in torchvisions (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11731

Immediate action

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

pip uninstall torchvisions

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-11-byted-dast

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
typosquatting
dependency-confusion

Malicious versions

1 flagged

94.6

Indicators of compromise (SHA-256)

ca1d0a04bc498d77c6868705c106e6f7850621dde352fc817af391356e3cef16

f5f8d8f067fb2c64e9684b206bfea00706ce52c39f7a9935245fbd8217482af6

51134ba41129052e6c7163c273094867918aff7ffc9579a3834f3febb74b44d7

aae12ce2e4f5ad0732bf9ccabd8841b47cc2d689121e1bacd20b381746e31b13

f55a3dfa0009889ec678036121ddfdc4e14e35c9ff3fbf5d2dd3875559e60f9a

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 torchvisions (version 94.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging torchvisions across your stack and pipelines.
If you installed it — respond
torchvisions 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 torchvisions 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 torchvisions 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. torchvisions on PyPI has been identified as a malicious package (version 94.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-111902024-11-byted-dastRLUA-2026-00831

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks torchvisions-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