Which versions of mvdream-threestudio are malicious?

The following PyPI versions of mvdream-threestudio are flagged malicious: 912.6. Treat any of these as compromised.

How do I remediate mvdream-threestudio if I installed it?

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

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

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

Malicious package

mvdream-threestudioPyPI

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

MAL-2024-11643

Immediate action

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

pip uninstall mvdream-threestudio

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

912.6

Indicators of compromise (SHA-256)

57c333404b04a050afd936329fbeb56acb5fc8755a7319b8ffceafd3beb1f50e

62f6bda693c20f52a3857f3276c67a9a1b8a9bd413871aa384e4db03b4e375e1

609ae3c19c5da8545336e0466e565db2d2ff6590b1a3bc1a089f3614344969b8

0b1f1a6a854a4cbc87f0a05e659379ac324715334309ff061f460e52722ba28a

9dcd8f8309df894ffd2d0e88d38f086ce7ba77eb41fbe43465c3d5c9c91807f9

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

Campaign

RLMA-2024-110992024-11-byted-dastRLUA-2026-00545

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks mvdream-threestudio-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