Which versions of midi-melody-extractions are malicious?

The following PyPI versions of midi-melody-extractions are flagged malicious: 94.6. Treat any of these as compromised.

How do I remediate midi-melody-extractions if I installed it?

midi-melody-extractions 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 midi-melody-extractions — how do I know if it already compromised me?

If midi-melody-extractions 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 midi-melody-extractions part of a known attack campaign?

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

Malicious package

midi-melody-extractionsPyPI

Malicious code in midi-melody-extractions (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11634

Immediate action

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

pip uninstall midi-melody-extractions

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)

48bcbc41ba90e5674b667422455065adcc7feaec4bc432f58f69da9f0f6c04b1

b38a7505eec0fc02a6dc8c1f31a0b8394f04af6fd209047d8885cd250c8ce623

8cf5fe50a15b36c41406e9d04f254b0acae240897b5ad49b1165228613cb036a

f9aeb4236154a8c26f1cb93b3f341bf4a7d5555085339be18d93e06b3e1bc5ff

d3e419fe06682e5eedf9622ff25854d1fb7300003ec1ef8d60927d1e1f1c645f

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

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks midi-melody-extractions-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