Which versions of maliinn are malicious?

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

How do I remediate maliinn if I installed it?

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

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

Yes — maliinn is associated with the RLMA-2025-03636, 2025-07-malimalo 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 maliinn 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 maliinn (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging maliinn across your stack and pipelines.

Malicious package

maliinnPyPI

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

MAL-2025-5655

Immediate action

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

pip uninstall maliinn

What this malware does

The only goal of the package is to execute a webhook or a suspicious file during installation.

Closely related to 2025-07-0x9xnx - created after previous packages were quarantined, similar names, similar usage, but no clearly malicious parts.

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: 2025-07-malimalo

Reasons (based on the campaign):

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

The OpenSSF Package Analysis project identified 'maliinn' @ 0.0.1 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c8969b947b2c4354b8462ee50241fa2060148bf6f9808f78a5497352a4862830

63e4167afdc152877780798be8dbf1d83992a7669b23c02b061d25f88b12d921

7789857d2d4c9be8906965ed9769911136732c20b7df677153b0ca64a973bdf5

dea697dc03b11e99e6895070c9fa053b8db92510a03201f9545dcb25bd373199

fa02e6bb5d0438d89e01ebb160bc15b8f81f918d7bd71264983584b0939f4142

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 maliinn (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging maliinn across your stack and pipelines.
If you installed it — respond
Remove maliinn 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 maliinn 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 maliinn 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. maliinn 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-2025-036362025-07-malimalo

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

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