# MAL-2026-18095: Malicious code in resion (PyPI)


- **Type:** Malicious package
- **Package:** `resion` (PyPI)
- **Published:** 20 Oct 2026

## What is MAL-2026-18095?

MAL-2026-18095 is a malicious package in resion, published on 20 Oct 2026. 

### Official description

No a static rule matches were produced for this package version, and no concrete behavioral evidence of credential access, install-time code execution, outbound exfiltration, backdoor, or silent-relay was identified in the available artifacts. The package coordinate (resion 22.0.1 on PyPI) is otherwise unremarkable from the information available; no attacker-controlled destination, no lifecycle hook performing network or filesystem actions outside the package's own directory, and no shipped third-party or author credential has been identified.

Description: In this campaign, the main package (resion) has an embeded pickle disguised as a config. A related dependency (pafex) contains code to load the pickle. During unpickling, malicious code embeded in the pickle file is automatically executed. It then establishes persistence via a PTH file and downloads the next stage payload. During analysis, the final remote payload was just a stub

---

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

Campaign: 2026-10-webreader

Reasons (based on the campaign):

 - files-exfiltration

 - obfuscation

 - The malicious code is intentionally included in a dependency of the package

 - Downloads and executes a remote malicious script.

 - The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.

 - rat

 - persistence

 - abuses-pth

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

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

## Sources

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

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