Which versions of byted-torch-monitor are malicious?

The following PyPI versions of byted-torch-monitor are flagged malicious: 0.0.1, 0.2. Treat any of these as compromised.

How do I remediate byted-torch-monitor if I installed it?

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

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

Yes — byted-torch-monitor is associated with the RLMA-2025-02558, 2025-04-byted-torch-monitor, RLUA-2026-00169 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 byted-torch-monitor 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 byted-torch-monitor (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging byted-torch-monitor across your stack and pipelines.

Malicious package

byted-torch-monitorPyPI

Malicious code in byted-torch-monitor (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-4207

Immediate action

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

pip uninstall byted-torch-monitor

What this malware does

During installation, a website with the current working dir is being called. It looks like something between spam and pentest as the website is most probably not in the control of the uploader. The package has no other purpose

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: 2025-04-byted-torch-monitor

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.

Malicious versions

2 flagged

0.0.10.2

Indicators of compromise (SHA-256)

97ca05915cbd9481ad28e6e29a9965a2bf4895dc9a2c547586efd18a5cf85030

84170246a3494973ec0e0f64e49e8a584f1c4b1cc3d7b5c0aaa8569595ef7a29

8c2b83888c7fcb79b930eaecb1a538d27a131ab415c0b756f84c7071d5a0935b

fffb9c9209de11a5f0058a91c1d3738c0134a66163ee35dbb9eec8aa15bafb73

29c9c582c79834ba98de729fb7a09cf325bd43f2e6e8e24b1a05eecfb2852ac1

f5500c7b17a11d7cabe3b64ebe8126a448b9f0e5fe8ba180db37614580df5925

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

Campaign

RLMA-2025-025582025-04-byted-torch-monitorRLUA-2026-00169

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks byted-torch-monitor-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