Malicious code in mrcl2 (PyPI)
Published Sources: OSV (Schadpakete)
- Malicious package
What is affected, what to do
On import of the MRCL2 package, __init__.py loads.core, which at module top level calls os.listdir('.') to enumerate the installer's current working directory and opens a TCP socket to the hardcoded host ejwdi-13-205-45-209.run.pinggy-free.link on port 40371, sending the directory listing to that endpoint. The destination is an ephemeral pinggy.link tunnel unrelated to the package's stated 'Document integrity utility' purpose, and the beacon fires on any import with no consent, no configuration, and no documented behavior.
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
PyPImrcl2
“mrcl2” 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.1
- 1.0.2
- 1.0.3
- 1.0.4
- 1.0.5
purl: pkg:pypi/mrcl2
Sources (5)
amazon-inspector
IN-MAL-2026-022931Versions from this source: 1.0.5
sha256: 5534383c960c9f05ae518d4940d06ef85e9eb8df3298070e859a9d366ccb0089
amazon-inspector
IN-MAL-2026-022928Versions from this source: 1.0.2
sha256: 925e04583c4e91821d2680e0d4b83d2a93279e98e93c58f926e9a9a5b767c85e
amazon-inspector
IN-MAL-2026-022930Versions from this source: 1.0.1
sha256: 94468c8a4cc610b62f3609247b14a0559159c0609e49c3119c4414016c22992e
amazon-inspector
IN-MAL-2026-022933Versions from this source: 1.0.3
sha256: c1b73cc67232ca98fb2ac5004d19268397a12c922eadf2b6ddcce0e5bc45ac9d
amazon-inspector
IN-MAL-2026-022929Versions from this source: 1.0.4
sha256: ec3d46c2bde8cb24c00a6d3fbf4efc912644488e11095244b75ac3f0f22df4d6
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
On import of the MRCL2 package, __init__.py loads.core, which at module top level calls os.listdir('.') to enumerate the installer's current working directory and opens a TCP socket to the hardcoded host ejwdi-13-205-45-209.run.pinggy-free.link on port 40371, sending the directory listing to that endpoint. The destination is an ephemeral pinggy.link tunnel unrelated to the package's stated 'Document integrity utility' purpose, and the beacon fires on any import with no consent, no configuration, and no documented behavior. In CI and developer environments the working directory frequently contains sensitive project file names, making this an import-time reconnaissance exfiltration channel.