Which versions of malicus are malicious?

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

How do I remediate malicus if I installed it?

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

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

Yes — malicus is associated with the RLMA-2025-03635, 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 malicus 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 malicus (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 malicus across your stack and pipelines.

Malicious package

malicusPyPI

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

MAL-2025-5654

Immediate action

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

pip uninstall malicus

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 'malicus' @ 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)

a33ca8f3dec153ea010973822a2919bfa0530325bf4b037096177eb3c6ba9aed

511a0df9ce62865e7fe9d9ab88084449ca162955e421d25e18faea4a42d8cb02

c82c6aaa8ce5fca384275ee10590977703f1b95785ff710809c4b28617464e52

d151385056670ff22bfb80dc356c10ff622a77e115f8d81ee5f066220e05fda1

d9368e68116db74a18b2468d7c138dec41ea67b55922d40ceaa5acf939589e48

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 malicus (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 malicus across your stack and pipelines.
If you installed it — respond
Remove malicus 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 malicus 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 malicus 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. malicus 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-036352025-07-malimalo

References

bad-packages.kam193.eu

Credits

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

Detect & block this

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