Which versions of metricboxlite are malicious?

The following PyPI versions of metricboxlite are flagged malicious: 1.0, 2.0. Treat any of these as compromised.

How do I remediate metricboxlite if I installed it?

metricboxlite is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed metricboxlite — how do I know if it already compromised me?

If metricboxlite was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is metricboxlite part of a known attack campaign?

Yes — metricboxlite is associated with the GENERIC-standard-pypi-install-pentest, IN-MAL-2026-019651, IN-MAL-2026-019838 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find metricboxlite across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for metricboxlite (2 malicious versions).

Malicious package

metricboxlitePyPI

Advisory published Sep 4, 2026Updated Sep 9, 2026

metricboxlite is a confirmed malicious PyPI package (MAL-2026-15931) that steals credentials and exfiltrates sensitive data (malicious versions 1.0, 2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in metricboxlite (PyPI)

MAL-2026-15931

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

pip uninstall metricboxlite

What this malware does

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.

Malicious versions

2 flagged

1.02.0

Indicators of compromise (SHA-256)

83407b9909ebc137e4d47fbb7fe2672a5920dd22bfd7d86ce8edb536bdd5fcab

b071475bfddef4e7b1637eba0ff65de0aa7841ac460bcca6a1892d349a38c073

d5a511a75c8c42dcd677dd3814265d3befefa7f339bdc6b0336788635813e837

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for metricboxlite (2 malicious versions).
If you installed it — respond
metricboxlite is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If metricboxlite was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. metricboxlite on PyPI has been identified as a malicious package (versions 1.0, 2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-standard-pypi-install-pentestIN-MAL-2026-019651IN-MAL-2026-019838

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks metricboxlite-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database