Which versions of plutotestingagain are malicious?

The following PyPI versions of plutotestingagain are flagged malicious: 0.0.0. Treat any of these as compromised.

How do I remediate plutotestingagain if I installed it?

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

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

Yes — plutotestingagain is associated with the RLMA-2024-04337, RLUA-2024-08765 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 plutotestingagain across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for plutotestingagain (version 0.0.0).

Malicious package

plutotestingagainPyPI

plutotestingagain is a confirmed malicious PyPI package (MAL-2024-5555) that executes malicious code on install (malicious version 0.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in plutotestingagain (PyPI)

MAL-2024-5555

Immediate action

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

pip uninstall plutotestingagain

Malicious versions

1 flagged

0.0.0

Indicators of compromise (SHA-256)

69c53e2eecf717d5ce95f9b22368fd5b7aa157c64e302163351c24ff4a159ca7

dff1e72fa0805c1b0d4f803c52f48f8f43f693e4a662d2da9f17649b22194ffb

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for plutotestingagain (version 0.0.0).
If you installed it — respond
Remove plutotestingagain 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 plutotestingagain 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. plutotestingagain on PyPI has been identified as a malicious package (version 0.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-04337RLUA-2024-08765

Credits

ReversingLabs · finder

Detect & block this

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