# MAL-2026-15931: Malicious code in metricboxlite (PyPI)


- **Type:** Malicious package
- **Package:** `metricboxlite` (PyPI)
- **Published:** 4 Sep 2026

## What is MAL-2026-15931?

MAL-2026-15931 is a malicious package in metricboxlite, published on 4 Sep 2026. 

### Official description

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.

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.

## What should I do about MAL-2026-15931?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-15931 is a malicious package: metricboxlite (PyPI). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-15931/ (Markdown: https://insights.sbomify.com/MAL-2026-15931/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-15931

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-15931/
Summaries are generated and may contain mistakes; the official description above is the record.