# MAL-2026-5841: Malicious code in twrap-toolkit (PyPI)


- **Type:** Malicious package
- **Package:** `twrap-toolkit` (PyPI)
- **Published:** 15 Jun 2026

## What is MAL-2026-5841?

MAL-2026-5841 is a malicious package in twrap-toolkit, published on 15 Jun 2026. 

### Official description

twrap_toolkit/__init__.py defines _get_payload() which issues a plaintext HTTP request to http://194.5.152.9:8080/hacks/textwrap-toolkit/textwrap_toolkit/__init__.py and passes the response body to exec() inside the package's only public API surface (format_block() and align_columns()). Any caller of the documented API executes attacker-controlled Python with no TLS, no pinning, and no integrity check, granting full remote code execution to the operator of 194.5.152.9. The package name and the attacker-controlled URL path both impersonate the legitimate 'textwrap-toolkit' utility, indicating a typosquat designed to lure installations into the dropper. Installing this package and invoking its advertised functions yields arbitrary code execution as the calling user.

During import, package downloads and executes an obfuscated script. The code then adds a new authorized SSH key and reports back the IP of the current environment. After that, the code also attempts to exfiltrate cryptocurrency wallet data

---

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

Campaign: 2026-06-textwrap-toolkit-stager

Reasons (based on the campaign):

 - backdoor

 - obfuscation

 - crypto-related

 - Downloads and executes a remote malicious script.

 - exfiltration-crypto

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

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-5841 is a malicious package: twrap-toolkit (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-5841/ (Markdown: https://insights.sbomify.com/MAL-2026-5841/index.md)
```

## Sources

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

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