Which versions of reqcrypts are malicious?

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

How do I remediate reqcrypts if I installed it?

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

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

Yes — reqcrypts is associated with the 2026-08-reqcrypt, IN-MAL-2026-018496, IN-MAL-2026-018495 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 reqcrypts 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 reqcrypts (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging reqcrypts across your stack and pipelines.

Malicious package

reqcryptsPyPI

reqcrypts is a confirmed malicious PyPI package (MAL-2026-14341) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1, 0.1.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in reqcrypts (PyPI)

MAL-2026-14341

Immediate action

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

pip uninstall reqcrypts

What this malware does

reqcrypts is published as a drop-in HTTP client (import reqcrypts; reqcrypts.get(url)) but its RequestHandler wraps every JSON response through a PayloadManager that base64-decodes a _payload field from the response body and passes it to exec() on the caller's Python interpreter, then deletes the field to hide the execution. Payload execution and silent mode are on by default. Any HTTP server the caller reaches (including MITM or redirect targets) can therefore run arbitrary Python code on the installer's host by returning a JSON body containing a _payload key. The package additionally exports top-level add_payload(trigger, code), set_default_payload(code), and enable_payloads helpers that store arbitrary Python source and feed it to the same exec() sink when a request endpoint matches the registered trigger, giving a second covert code-execution path. The docstring describes this as 'automatic silent payload execution'. Any application using reqcrypts as its HTTP client is exposed to remote code execution from any responding server.

The package contains a hidden backdoor. The promised functionality is an HTTP request library with some additional functions. On every usage, code secretly checks for the presence of specific fields in the response, and if they are found, their content is secretly executed.

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

Campaign: 2026-08-reqcrypt

Reasons (based on the campaign):

backdoor

Malicious versions

4 flagged

0.1.00.1.10.1.20.1.3

Indicators of compromise (SHA-256)

516430200454879e0449beefe11b3981553ecb85df586ed09d8057ea94016c46

d53882b2c7d871e0f23318b5f65207af815ce41362267a935b5f9dfaa9c4fa9d

7fb4e239b6344dfe684483344d4d1a2da013a4d506b78d81e9096c6b31a690ae

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 reqcrypts (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging reqcrypts across your stack and pipelines.
If you installed it — respond
reqcrypts 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 reqcrypts 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 reqcrypts 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. reqcrypts on PyPI has been identified as a malicious package (versions 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

2026-08-reqcryptIN-MAL-2026-018496IN-MAL-2026-018495

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

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