Which versions of donotinstallthisistest5 are malicious?

The following PyPI versions of donotinstallthisistest5 are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate donotinstallthisistest5 if I installed it?

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

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

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

Malicious package

donotinstallthisistest5PyPI

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

MAL-2025-41664

Immediate action

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

pip uninstall donotinstallthisistest5

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

1 flagged

0.1.0

Indicators of compromise (SHA-256)

b6d9c014377fd015514c9fbb6feb5ef84c1e195da710a549d1c603a1f3fdb386

dd8e31616b6260561056f48598bf5eab38953d6a828c634785631b6b7f63d1e0

69bdb408fdc5c6421ad916ee033682fdeb9c45276fa003370aa364afc28a8ec8

be32a78257e94ea85f8476963cdf0388a39549c60de41d3fd4034fb3dd27ab11

b56fa30c416305ccce246772185ba0f17ef67b0d2a922366f3db83f199f6d8e1

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

Campaign

RLMA-2025-04156GENERIC-standard-pypi-install-pentestRLUA-2026-00280

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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