Which versions of music-source-separation are malicious?

The following PyPI versions of music-source-separation are flagged malicious: 912.6. Treat any of these as compromised.

How do I remediate music-source-separation if I installed it?

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

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

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

Malicious package

music-source-separationPyPI

Malicious code in music-source-separation (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11641

Immediate action

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

pip uninstall music-source-separation

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)

27aa228109cf70c5226f2c10225c4697bb56288d905549dc404a20364b9fbb16

de8fad1d62cfed14d4624459b1b4775959f1e85af501f42c7cb6858cf62e613a

a4aa4c5d893735fb71d4983056b6d254f087a4f5c82df6976e2efdab41f0c9f2

8304b40777ccfc333381d5be606e49f9a4ba8b1d665e1d064451c4f180b2f122

8a6e15c40707a8c1ff76167c73b865492f432769887f67138b59f920e0065113

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

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks music-source-separation-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