Which versions of imad213insta are malicious?

The following PyPI versions of imad213insta are flagged malicious: 213.1, 213.2. Treat any of these as compromised.

How do I remediate imad213insta if I installed it?

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

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

Yes — imad213insta is associated with the RLMA-2025-05608 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 imad213insta across my projects, lockfiles, and CI pipelines?

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

Malicious package

imad213instaPyPI

Advisory published Dec 1, 2025Updated Dec 2, 2025

imad213insta is a confirmed malicious PyPI package (MAL-2025-191639) that executes malicious code on install (malicious versions 213.1, 213.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in imad213insta (PyPI)

MAL-2025-191639

Immediate action

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

pip uninstall imad213insta

Malicious versions

2 flagged

213.1213.2

Indicators of compromise (SHA-256)

e86062a77d6dde5a70d8686db1e883c732bab8e803d854bc24296255b7aeee36

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05608

Credits

ReversingLabs · finder

Detect & block this

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