Malicious code in metricboxlite (PyPI)

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

Source: amazon-inspector (d5a511a75c8c42dcd677dd3814265d3befefa7f339bdc6b0336788635813e837)

MetricBoxLite 1.0 collects the installer's username (getpass.getuser) and hostname (socket.gethostname), JSON-encodes them, and POSTs the payload to a hardcoded remote endpoint at https://kznkrxfzy4xgib6ejfh8etegndp3kwguf.oast.invalid/collect. The beacon fires from two independent paths: setup.py calls the reporter at module top level, so it runs during pip install of the sdist, and metricboxlite/init.py performs the same collect-and-POST at top level, so any import metricboxlite also phones home. Network errors are silently swallowed. The destination is an OAST/out-of-band-callback host that is not first-party to the package or its ecosystem, and the collected fields are installer identity rather than package operational data.

Source: kam193 (83407b9909ebc137e4d47fbb7fe2672a5920dd22bfd7d86ce8edb536bdd5fcab)

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

• The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

• The package overrides the install command in setup.py to execute malicious code during installation.