Which versions of testing1232 are malicious?

The following PyPI versions of testing1232 are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate testing1232 if I installed it?

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

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

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

Search your lockfiles and build artifacts for testing1232 (version 0.0.1).

Malicious package

testing1232PyPI

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

Malicious code in testing1232 (PyPI)

MAL-2024-6114

Immediate action

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

pip uninstall testing1232

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

65d4597527d26e54bde17ceef57e210a8d4fb84fff908fe03a81310384658b74

a20efd02e46e96c26374f4ead55f4cb6783d1d29af3909a158b6954d0e984c4b

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-04918RLUA-2024-09387

Credits

ReversingLabs · finder

Detect & block this

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