Which versions of no-install-test-noinst are malicious?

The following PyPI versions of no-install-test-noinst are flagged malicious: 2.0.10. Treat any of these as compromised.

How do I remediate no-install-test-noinst if I installed it?

Remove no-install-test-noinst from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed no-install-test-noinst — how do I know if it already compromised me?

If no-install-test-noinst was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is no-install-test-noinst part of a known attack campaign?

Yes — no-install-test-noinst is associated with the RLMA-2024-04196, RLUA-2024-08570 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 no-install-test-noinst across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for no-install-test-noinst (version 2.0.10).

Malicious package

no-install-test-noinstPyPI

no-install-test-noinst is a confirmed malicious PyPI package (MAL-2024-5414) that executes malicious code on install (malicious version 2.0.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in no-install-test-noinst (PyPI)

MAL-2024-5414

Immediate action

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

pip uninstall no-install-test-noinst

Malicious versions

1 flagged

2.0.10

Indicators of compromise (SHA-256)

4963438289f0d46e9fd51d119ecb3460cd9c837ebf47dffb6c85a99b9572f358

c5ada796b2f8c6f5412ace4c808191a655e673fcff647540ce8bf9dfa5df7561

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for no-install-test-noinst (version 2.0.10).
If you installed it — respond
Remove no-install-test-noinst from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If no-install-test-noinst was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. no-install-test-noinst on PyPI has been identified as a malicious package (version 2.0.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-04196RLUA-2024-08570

Credits

ReversingLabs · finder

Detect & block this

O3 blocks no-install-test-noinst-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database