Which versions of donotinstall are malicious?

The following PyPI versions of donotinstall are flagged malicious: 1, 1.0. Treat any of these as compromised.

How do I remediate donotinstall if I installed it?

donotinstall establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed donotinstall — how do I know if it already compromised me?

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

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

Malicious package

donotinstallPyPI

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

MAL-2025-191622

Immediate action

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

pip uninstall donotinstall

What this malware does

Package contains obfuscated reverse shell. However, it connects with a local IP only, thus it's much more a test than a malicious action

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: 2025-10-donotinstall

Reasons (based on the campaign):

The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.
obfuscation

Malicious versions

2 flagged

11.0

Indicators of compromise (SHA-256)

94ed4ebff18057da5526637d1150d8cc470f20112bacca2f43bab949d14216f2

fecfc822a8976103368c32882bbc7c420938c161e019165d9acd67cb08e2f45a

a0c56680f6f4db81ec1ad0691253d592055a3581b00e9c93e3dfd6d448b63212

00b412c8982f5407430b6b2adb21986e7460d0959c429e13997fc14072f9c0e7

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for donotinstall (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging donotinstall across your stack and pipelines.
If you installed it — respond
donotinstall establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If donotinstall 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 donotinstall 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. donotinstall on PyPI has been identified as a malicious package (versions 1, 1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-055902025-10-donotinstallRLUA-2026-00279

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks donotinstall-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring