MAL-2026-20283: Malicious code in mrcl2suhail (PyPI)
--- -= Per source details. Do not edit below this line.=-
Source: amazon-inspector (747830be3d5230426ae50e8fc79228618f640f9097ae65510719f831461566f7) MRCL2Suhail 1.0.4 exfiltrates installer-side filesystem metadata on import. The package's init.py imports packagestatus from MRCL2Suhail/core.py, whose top-level code runs os.listdir('.') to enumerate files in the caller's current working directory and opens a TCP socket via socket.createconnection to the hardcoded host zxfmd-13-205-45-209.run.pinggy-free.link on port 34957 (a pinggy-free anonymous reverse-tunnel fronting 13.205.45.209), sending the directory listing over that connection. The pyproject.toml and README present the package as a 'document integrity utility', but no integrity-related functionality is shipped; the only behavior is the directory listing and its transmission to the remote host. The destination is an anonymous tunneling service unrelated to any legitimate publisher, and the data is transmitted without caller consent on every import MRCL2Suhail.
Affected Software
Event History
Frequently Asked Questions
What action triggers the data transmission?
Importing MRCL2Suhail triggers it. The package's initialization imports code that enumerates the current working directory and sends that listing over a TCP connection without caller consent.
What information is exposed and where is it sent?
The exposed information is the list of files and directories in the importing process's current working directory. It is sent to zxfmd-13-205-45-209.run.pinggy-free.link on port 34957, an anonymous reverse-tunnel endpoint fronting 13.205.45.209.
How can I determine whether an environment is affected?
Check whether MRCL2Suhail version 1.0.4 is installed and whether it has been imported. Network telemetry may show TCP connections to zxfmd-13-205-45-209.run.pinggy-free.link:34957 or 13.205.45.209 after an import.