Which versions of windowsrequir are malicious?

The following PyPI versions of windowsrequir are flagged malicious: 1.0.2. Treat any of these as compromised.

How do I remediate windowsrequir if I installed it?

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

If windowsrequir was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is windowsrequir part of a known attack campaign?

Yes — windowsrequir is associated with the RLMA-2025-05643, 2025-10-windowsrequir, RLUA-2026-00931 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 windowsrequir across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for windowsrequir (version 1.0.2).

Malicious package

windowsrequirPyPI

Advisory published Oct 26, 2025Updated Mar 19, 2026

windowsrequir is a confirmed malicious PyPI package (MAL-2025-191665) that steals credentials and exfiltrates sensitive data (malicious version 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in windowsrequir (PyPI)

MAL-2025-191665

Immediate action

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

pip uninstall windowsrequir

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

1 flagged

1.0.2

Indicators of compromise (SHA-256)

b2d199a1a33df939f3accf1d9998b81056910cf2364c567bfbbcd305c9533a2e

ec04476a65a75afba7dec1ff16b538a6c135a5a67b55b0396fe84bc24572e0da

8b1e2404307bae09dee3c7fe01e272b488ca2da014d14ad2a740ed76c89634e8

35e487286749e88376e5ea97f5897b7bb9a4b8b294447c5582ffea2be510b0e8

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for windowsrequir (version 1.0.2).
If you installed it — respond
windowsrequir 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 windowsrequir was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. windowsrequir on PyPI has been identified as a malicious package (version 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-056432025-10-windowsrequirRLUA-2026-00931

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database