Supply chain · pip · High

Malicious 'tallyboxlite' PyPI Package Exfiltrates Basic Host Information

Threat Engine Auto-Feed · data current as of 2026-09-01

A malicious package, 'tallyboxlite' version 1.0, has been identified in the PyPI ecosystem. Installation or import of this package leads to the exfiltration of basic host information, posing a supply-chain risk to Python development environments.

  • Package: pip / tallyboxlite
  • Affected versions: = 1.0
  • Severity: critical
  • Reach: unknown
  • Exposure: 65/100 (High)

What happened — Credential / secret theft

The 'tallyboxlite' package (version 1.0) on PyPI contains malicious code designed to exfiltrate basic information about the host system upon installation or module import. The package serves no other legitimate purpose.

How the attack works

This is a supply-chain attack where a malicious package is introduced into a public registry. The attack leverages the package's `setup.py` to execute code during installation or through direct module import, enabling the exfiltration of system data. This method bypasses typical application-level security by compromising a dependency.

Who's exposed

Profiles most at risk

  • Development teams using Python and PyPI
  • CI/CD pipelines that automatically pull Python dependencies
  • Organizations with internal mirrors that sync from PyPI

Conditions that increase exposure

  • Unpinned dependencies in `requirements.txt` or `pyproject.toml` that could resolve to `tallyboxlite` version 1.0
  • Lack of dependency lockfiles (`Pipfile.lock`, `poetry.lock`)
  • Automated build processes that install new or updated dependencies without review
  • Direct installation of `tallyboxlite` version 1.0

Blast-radius scenarios

  • An attacker could gain basic reconnaissance data about compromised build environments or developer machines.
  • Successful installation could lead to the exfiltration of IP addresses, usernames, and other foundational system details, providing initial access or intelligence for further attacks.

What to do (defensive)

Detect

  • Scan dependency trees for `tallyboxlite` version 1.0.
  • Monitor network traffic for unusual outbound connections from build systems or developer machines after dependency installation.
  • Review `setup.py` files of new or updated dependencies for suspicious commands or overrides.

Contain

  • Immediately quarantine any systems found to have installed `tallyboxlite` version 1.0.
  • Block `tallyboxlite` version 1.0 at the network perimeter and within internal package registries.
  • Isolate build environments and developer workstations that may have pulled the package.

Remediate

  • Remove `tallyboxlite` version 1.0 from all affected systems and rebuild applications with verified dependencies.
  • Force all Python projects to use pinned dependencies and lockfiles to prevent accidental installation of malicious versions.
  • Educate developers on the risks of untrusted packages and the importance of dependency verification.

Frontier verdict — High

Prioritize immediate detection and removal of 'tallyboxlite' version 1.0 due to its critical severity and host information exfiltration capabilities.

Sources

For detection-engineering and awareness only · point-in-time · not security advice · sourced from the GitHub Advisory Database.