Which versions of mangasee123 are malicious?

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

How do I remediate mangasee123 if I installed it?

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

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

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

Search your lockfiles and build artifacts for mangasee123 (2 malicious versions).

Malicious package

mangasee123PyPI

mangasee123 is a confirmed malicious PyPI package (MAL-2024-5348) that executes malicious code on install (malicious versions 0.0.1, 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mangasee123 (PyPI)

MAL-2024-5348

Immediate action

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

pip uninstall mangasee123

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

da5658edd6c7d4335f04247153ee927d70bdc3aaccad2e4925fa4d53a6c7bab3

12ff0fa2a3a18db02f9255d5feb83b62f3d70db662bfdf15394a8e618e47c694

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-04130RLUA-2024-08494

Credits

ReversingLabs · finder

Detect & block this

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