Which versions of install-all-setup are malicious?

The following PyPI versions of install-all-setup are flagged malicious: 0.1.0, 0.1.1. Treat any of these as compromised.

How do I remediate install-all-setup if I installed it?

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

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

Yes — install-all-setup is associated with the RLMA-2025-05609, 2025-10-windowsrequir, RLUA-2026-00426 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 install-all-setup 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 install-all-setup (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging install-all-setup across your stack and pipelines.

Malicious package

install-all-setupPyPI

Malicious code in install-all-setup (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191640

Immediate action

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

pip uninstall install-all-setup

What this malware does

Package downloads and runs an obfuscated bat file, which executes malicious activity according to VirusTotal results.

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

Campaign: 2025-10-windowsrequir

Reasons (based on the campaign):

impersonation
Downloads and executes a remote malicious script.
malware

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

e82ea3bfe177e3a52180f82acba72f98c9b10f04e97ea0ae8dc74d1c004ca45d

03401206aa55bda1cc26afad6203380a749c97da2240e9569300d7e521a8d91a

519885ab1e79055139dd279d8e9bf603b4f1d0c0f3f6d3c90231c934f26bbb60

e8a9d972780917c906493881066e1cc7bce18f30732f1b8e8b65b708630fdb0d

52619318269cf4f857dcfb1bbd7003ad52d53fea1cd7e7b74fd0271eb961366e

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

Campaign

RLMA-2025-056092025-10-windowsrequirRLUA-2026-00426

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks install-all-setup-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