Malicious code in mrcl2suhail (PyPI)
Published Sources: OSV (Schadpakete)
- Malicious package
What is affected, what to do
MRCL2Suhail 1.0.4 exfiltrates installer-side filesystem metadata on import. The package's __init__.py imports package_status 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.create_connection 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.
Uninstall the package, isolate affected environments and rotate credentials that were available during installation.
Not sure whether and how you are affected? Ask a question about this vulnerability
Malicious package
PyPImrcl2suhail
“mrcl2suhail” is registered as malicious in the PyPI repository. Anyone who installed the package should uninstall it immediately, isolate affected environments and rotate credentials that were present during installation.
Affected versions (5)
- 1.0.0
- 1.0.1
- 1.0.2
- 1.0.3
- 1.0.4
purl: pkg:pypi/mrcl2suhail
Sources (5)
amazon-inspector
IN-MAL-2026-022932Versions from this source: 1.0.1
sha256: 523567bd35fdb073dc4c811909210894baf205da91cb88e561a2895eec9d21fc
amazon-inspector
IN-MAL-2026-022937Versions from this source: 1.0.3
sha256: e8d10d12fbda8db89f4efb86efbc34cfefb05b542b095fd7b9e1a68aedebf025
amazon-inspector
IN-MAL-2026-022935Versions from this source: 1.0.4
sha256: 747830be3d5230426ae50e8fc79228618f640f9097ae65510719f831461566f7
amazon-inspector
IN-MAL-2026-022936Versions from this source: 1.0.2
sha256: 935dcca8b52f6a04017173554c124da7a489f961450f6c19c0be289aac20b49d
amazon-inspector
IN-MAL-2026-022934Versions from this source: 1.0.0
sha256: a46fbd73dd43adf12b12cffccec79a5d46d58c26084648cc6421a78cefd24d27
The OSSF `malicious-packages` namespace lists packages flagged as malicious by static analysis or sandbox detonation. An entry here is a confirmed finding, not a suspicion.
Metrics
—
XIEM Effective CVSS
No value is available for this vulnerability.
—
CVSS v3
No value is available for this vulnerability.
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 30.00 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
MRCL2Suhail 1.0.4 exfiltrates installer-side filesystem metadata on import. The package's __init__.py imports package_status 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.create_connection 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`.