Which versions of reguestsc are malicious?

The following PyPI versions of reguestsc are flagged malicious: 2.34.2. Treat any of these as compromised.

How do I remediate reguestsc if I installed it?

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

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

Yes — reguestsc is associated with the 2026-07-reguestsc 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 reguestsc across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for reguestsc (version 2.34.2).

Malicious package

reguestscPyPI

Advisory published Jul 31, 2026Updated Jul 31, 2026

reguestsc is a confirmed malicious PyPI package (MAL-2026-11413) that steals credentials and exfiltrates sensitive data (malicious version 2.34.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in reguestsc (PyPI)

MAL-2026-11413

Immediate action

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

pip uninstall reguestsc

What this malware does

Clones of a legitimate library with injected code downloading and executing a malicious executable on import. Dynamic analysis identified it as salatstealer.

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

Campaign: 2026-07-reguestsc

Reasons (based on the campaign):

typosquatting
Downloads and executes a remote executable.
malware
clones-real-package
spyware-like
infostealer

Malicious versions

1 flagged

2.34.2

Indicators of compromise (SHA-256)

20e4ae2ce79408a65e9b4bb348c2d69e20eb6072e3641531e2ec5773f1bbddd6

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for reguestsc (version 2.34.2).
If you installed it — respond
reguestsc 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 reguestsc 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. reguestsc on PyPI has been identified as a malicious package (version 2.34.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-07-reguestsc

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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