# MAL-2026-14341: Malicious code in reqcrypts (PyPI)


- **Type:** Malicious package
- **Package:** `reqcrypts` (PyPI)
- **Published:** 21 Aug 2026

## What is MAL-2026-14341?

MAL-2026-14341 is a malicious package in reqcrypts, published on 21 Aug 2026. 

### Official description

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

## What should I do about MAL-2026-14341?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-14341 is a malicious package: reqcrypts (PyPI). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-14341/ (Markdown: https://insights.sbomify.com/MAL-2026-14341/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-14341

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-14341/
Summaries are generated and may contain mistakes; the official description above is the record.