Which versions of ibmodules are malicious?

The following PyPI versions of ibmodules are flagged malicious: 0.1.0, 0.1.1, 0.1.2. Treat any of these as compromised.

How do I remediate ibmodules if I installed it?

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

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

Yes — ibmodules is associated with the GENERIC-simple-tests, RLMA-2026-01683 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 ibmodules 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 ibmodules (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ibmodules across your stack and pipelines.

Malicious package

ibmodulesPyPI

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

MAL-2024-12290

Immediate action

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

pip uninstall ibmodules

What this malware does

Packages that might be part of testing for pentesting / malicious activity / joy, with suspicious activity that does not present any real harm.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-simple-tests

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

3 flagged

0.1.00.1.10.1.2

Indicators of compromise (SHA-256)

aaa59bd2a2d751fb9b3c426a7741871e79b6247ecefc8fe6d28279c62b3e5d3e

528799dcf6ef54776c89013435fe9dd3f4bd84ca5dd02a9defad3e9c86632e7c

372b929f27219a9cd22759fe626b35e49cbdd1a0871f6755b22ef257194bfaf4

fb2d8d8fcf8c195d4328bcadbf7064f7f66054ce74f3719eb2d00bf7fe5023ca

e2c8f8ea9f6b564d8d23a4501b2a559c28ca1158ffe0701344127c5b94b4cbf8

5a52dd136ae32bfd341bacf97b6765785a6b73c905707ac338eecc6e047e128f

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ibmodules (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ibmodules across your stack and pipelines.
If you installed it — respond
Remove ibmodules 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 ibmodules 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 ibmodules 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. ibmodules on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1, 0.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-simple-testsRLMA-2026-01683

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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