resion

Source: amazon-inspector (d1b4088658d04bc0725d06a035fa9d83254699e6c26ce3653433199de9b10821)
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.

Source: kam193 (2e9e3ce373adb26e45616eec47d727e557f5a696737cb2fbcaa66fb7dc7b7c3e)
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