MAL-2026-20282: Malicious code in mrcl2 (PyPI)

Published Nov 20, 2026
·
Updated

--- -= Per source details. Do not edit below this line.=-

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

Affected Software

1 affected component
pip/mrcl2=1.0.5, =1.0.2, =1.0.1, =1.0.3, =1.0.4

Event History

Nov 20, 2026
Advisory Published
via OSV·03:02 AM
Data Sourced
via OSV·03:02 AM
DescriptionAffected Software

Frequently Asked Questions

1

What systems are exposed to the outbound data transmission?

Any environment that imports MRCL2 is exposed, because the behavior runs during module import without consent, configuration, or documented activation. CI and developer environments are specifically at risk because their current working directories often contain sensitive project file names.

2

What does an attacker need to trigger the behavior?

The package only needs to be imported. At import time it enumerates the installer's current working directory and opens a TCP connection to the hardcoded host on port 40371 to send the directory listing.

3

Are default installations affected?

Yes. The network beacon is invoked at module top level during import, with no indicated opt-in setting or configuration requirement.

4

What can be done if the package cannot be removed immediately?

Avoid importing MRCL2, especially from directories containing sensitive project files. Restrict outbound TCP connectivity to the hardcoded destination and port 40371 where network controls permit.

5

How can defenders determine whether they may have been affected?

Review whether MRCL2 was imported and inspect network telemetry for TCP connections to ejwdi-13-205-45-209.run.pinggy-free.link on port 40371. Also assess the working directory used at the time of import, since its file names are the data enumerated and sent.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203