Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

audio-separator-forkPyPI

Malicious code in audio-separator-fork (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-9947
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall audio-separator-fork

What this malware does

Clones real package and hoddens an obfuscated code trying to run remote scripts as well as establish backdoor through SSH.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2024-08-fireindahole.fun

Reasons (based on the campaign):

  • backdoor

  • action-hidden-in-lib-usage

  • clones-real-package

  • obfuscation

  • dependency-confusion

Malicious versions

11 flagged
0.8.00.8.10.8.20.8.30.8.40.8.60.8.70.8.80.8.90.8.100.8.11

Indicators of compromise (SHA-256)

9de4b136e4620bf1f92f8a1d6b8fd206794988cc4137294a29829343d2e7ca1e
e04cac0386c4b2e16da6fff25b508ffb8d2c9449217afcc577bb0e26180e8075
c2fdb66a75c58bc11250d088e141d39a4d2bbf8be018db9bb0ca9fd219d7e257
e8aca8b13425ef648df88ece52941fb4094e305036e6aaf95e46278d039e9163
48edd97ea0faea28b66099d836ae41c3190e5c4fdc3493f0cf4f21d78c4a212e
957b022c3a55add562d358b44a56b8e97a7bd413a303cc5c70d9a66ae2cdebb9

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for audio-separator-fork (11 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging audio-separator-fork across your stack and pipelines.

  2. If you installed it — respond

    audio-separator-fork 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.

  3. Did it already run?

    If audio-separator-fork 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.

  4. How O3 protects you

    O3 blocks audio-separator-fork 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. audio-separator-fork on PyPI has been identified as a malicious package (versions 0.8.0, 0.8.1, 0.8.2, 0.8.3, 0.8.4, 0.8.6, 0.8.7, 0.8.8, and 3 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-078432024-08-fireindahole.funRLUA-2026-00119

References

Credits

  • Kamil Mańkowski (kam193)
  • ReversingLabs · finder

Detect & block this

O3 blocks audio-separator-fork-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

audio-separator-fork (PyPI) malicious package — MAL-2024-9947 | O3 Security