Which versions of midi-melady-extraction are malicious?

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

How do I remediate midi-melady-extraction if I installed it?

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

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

Yes — midi-melady-extraction is associated with the RLMA-2024-11087, 2024-11-byted-dast, RLUA-2026-00519 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-melady-extraction 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-melady-extraction (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-melady-extraction across your stack and pipelines.

Malicious package

midi-melady-extractionPyPI

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

MAL-2024-11632

Immediate action

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

pip uninstall midi-melady-extraction

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)

de6c871f65aa4cce7b41aace6a1492012eef5cf1d47ede204dd16148b9c8b2b2

47393010d50c730a2cae2fc4be4f01e39385f9f11250ca7cacea63d81d43cc47

2ea216ddb559e40724229a4744f930ac8f9189582a30c9151da9036cd1e8c8f4

c756e4e2d9fe364ce5006e9030ef014ca885d39a9b9ae7989a13f9135a526647

22ed37e9380c696bb188d8448c90648e288f6c0a192d0e2f68858b7c1968f9fb

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-melady-extraction (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-melady-extraction across your stack and pipelines.
If you installed it — respond
midi-melady-extraction 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-melady-extraction 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-melady-extraction 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-melady-extraction 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-110872024-11-byted-dastRLUA-2026-00519

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks midi-melady-extraction-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