Which versions of multiutils are malicious?

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

How do I remediate multiutils if I installed it?

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

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

Yes — multiutils is associated with the RLMA-2025-02514, RLUA-2025-02582, GENERIC-standard-pypi-install-pentest, RLUA-2026-00538 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 multiutils 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 multiutils (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging multiutils across your stack and pipelines.

Malicious package

multiutilsPyPI

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

MAL-2025-3451

Immediate action

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

pip uninstall multiutils

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

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-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

5 flagged

0.0.10.1.00.1.10.1.20.1.3

Indicators of compromise (SHA-256)

4008ba527fae3378f6541315bd9c241a5b8d0946dd275c17c21f491e677782f9

1181a86e088417cbeee9726f1976b467deed0d146583993f835fe3d978254fea

66426c7f896f9b6d1b5a61870b9422fad66f810bea71b7d7531e7b379a971a7e

4cf1aa7242b79df0848b6bac5a3d8a01fc2201dc43047cd5466108a2b81f3453

cf6bb407d9f58d185608149a65a89dc91457796d091f669e8976af0bcdbe77cb

b661819d2457bce1724f72534bb0177c09340b98d1302a78dda4385c4efb9677

e0f8743289fde7c183b9160056f5d3d34e60a08421f6e1ba0f328c851951c302

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 multiutils (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging multiutils across your stack and pipelines.
If you installed it — respond
multiutils 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 multiutils 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 multiutils 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. multiutils on PyPI has been identified as a malicious package (versions 0.0.1, 0.1.0, 0.1.1, 0.1.2, 0.1.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-02514RLUA-2025-02582GENERIC-standard-pypi-install-pentestRLUA-2026-00538

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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