Which versions of minemeld-core are malicious?

The following PyPI versions of minemeld-core are flagged malicious: 0.0.0, 0.9.31. Treat any of these as compromised.

How do I remediate minemeld-core if I installed it?

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

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

Yes — minemeld-core is associated with the GENERIC-standard-pypi-install-pentest, RLMA-2025-06575, RLUA-2026-00522 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 minemeld-core 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 minemeld-core (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging minemeld-core across your stack and pipelines.

Malicious package

minemeld-corePyPI

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

MAL-2025-191791

Immediate action

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

pip uninstall minemeld-core

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

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: GENERIC-standard-pypi-install-pentest

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.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

2 flagged

0.0.00.9.31

Indicators of compromise (SHA-256)

2e2f78a22a5b03be1348d7c22857f062788b83e17cf995955dc93ca37bda0d11

dfe7b8c00b3748b3fe38ffdf3bd69558abb58091ee3347d47003929976ceb457

252e425e15e2b598defc07336079de21a91f006ae0cbfcc7c7ecc744857b077f

c4676991268bd4e705388ed915b373d6493c729a962a8138b03bdb913cd0128b

877e270dc927ff31ce9d829d7b47b1b32e7120921ce9e0297d9af9be9a8cd0ff

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

Campaign

GENERIC-standard-pypi-install-pentestRLMA-2025-06575RLUA-2026-00522

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks minemeld-core-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