Which versions of mkdsli are malicious?

The following PyPI versions of mkdsli are flagged malicious: 3.0.0, 4.0.0, 5.0.0, 6.0.0, 7.0.0. Treat any of these as compromised.

How do I remediate mkdsli if I installed it?

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

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

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

Malicious package

mkdsliPyPI

Malicious code in mkdsli (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-945

Immediate action

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

pip uninstall mkdsli

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

5 flagged

3.0.04.0.05.0.06.0.07.0.0

Indicators of compromise (SHA-256)

b976b55c69dc445d815ae69f940820ea68f3ff0d874d7dd99eb8e11ce4cca6d9

33eacd088d60e9fa9f48402c32ca441703a9a94da9f78a1116b8ba3ba95132c8

196d1c4dba825b894b1e9708968b33e8f49523a93caa4dd839a05e0637f1716b

33c61715e1c2960cf7c7e02c7e235fd55add1d8bad6ee2b4a2168acd8e78aea3

b8a7974dd9bd6a36b7c3e3fe685b7d97a0e348b1325131acfb1bd4d5883a3da8

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

Campaign

RLMA-2025-00485GENERIC-standard-pypi-install-pentestRLUA-2026-00524

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks mkdsli-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