What does the imad213tools malware do?

Encrypted code offering massive sending Instagram followers. 1) besides of using some shady services to achieve the goal, it also exfiltrates saved Instagram credentials to a remote server; 2) the project page offers selling an "exploit" for Instagram servers Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2025-07-imad213tools Reasons (based on the campaign): - exfiltration-credentials - other - obfuscation

Which versions of imad213tools are malicious?

The following PyPI versions of imad213tools are flagged malicious: 1.0.0, 213. Treat any of these as compromised.

How do I remediate imad213tools if I installed it?

imad213tools is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed imad213tools — how do I know if it already compromised me?

If imad213tools was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is imad213tools part of a known attack campaign?

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

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for imad213tools (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging imad213tools across your stack and pipelines.

Malicious package

imad213toolsPyPI

Malicious code in imad213tools (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191764

Immediate action

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

pip uninstall imad213tools

What this malware does

Encrypted code offering massive sending Instagram followers.

besides of using some shady services to achieve the goal, it also exfiltrates saved Instagram credentials to a remote server;
the project page offers selling an "exploit" for Instagram servers

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-07-imad213tools

Reasons (based on the campaign):

exfiltration-credentials
other
obfuscation

Malicious versions

2 flagged

1.0.0213

Indicators of compromise (SHA-256)

c7749e01a147bee07679d7fddb4dc16b34399b6015b8fbc92352352687648751

2cddffd96538ab03979aa6404e3c946258e49677220c4820f3a8f0972b31cb17

3af3593bdc280b177375f0a66709b11dca8f66899289419f6ba368ee5b6579ee

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for imad213tools (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging imad213tools across your stack and pipelines.
If you installed it — respond
imad213tools is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If imad213tools was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks imad213tools before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. imad213tools on PyPI has been identified as a malicious package (versions 1.0.0, 213 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-07-imad213tools

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks imad213tools-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring