Which versions of torchs-visions are malicious?

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

How do I remediate torchs-visions if I installed it?

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

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

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

Malicious package

torchs-visionsPyPI

Malicious code in torchs-visions (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11730

Immediate action

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

pip uninstall torchs-visions

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)

2a7f06c79fdf2cbe3c62ea355364b855483370dbda197cd27b5cc03659dfbc70

012a2267653fc3502caab8dc4125007cbd966e814a289d8fa13ced16d3981901

55065e0cb0170fe8d242932d470508fb1013fa0cdba286b09bf8b239b3958533

28fd8ceca103ae2dbd365087365cc4559fc9b40ec524042495eceb1659788ef6

c60234da41d8fab2fbfce98d90936bdaebcdf9557401bf46d11e2795ef2d8181

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 torchs-visions (version 94.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging torchs-visions across your stack and pipelines.
If you installed it — respond
torchs-visions 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 torchs-visions 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 torchs-visions 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. torchs-visions 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-111892024-11-byted-dastRLUA-2026-00830

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks torchs-visions-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