Supply chain · pip · High

Malicious pip package 'dbt-sa-cli' (v0.0.1) exfiltrates host information

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

A malicious version 0.0.1 of the 'dbt-sa-cli' package in the pip ecosystem has been identified. Installation or import of this package leads to the exfiltration of basic host information, posing a risk of credential or secret theft. Organizations using this package should immediately assess their exposure and take mitigation steps.

  • Package: pip / dbt-sa-cli
  • Affected versions: = 0.0.1
  • Severity: critical
  • Reach: unknown
  • Exposure: 65/100 (High)

What happened — Credential / secret theft

The 'dbt-sa-cli' package, specifically version 0.0.1, was found to contain malicious code. Upon installation or import, this package is designed to exfiltrate basic information about the host system. The package's primary function appears to be this data exfiltration, with no other legitimate purpose.

How the attack works

This is a supply-chain attack where a malicious package is introduced into a public repository. The attack leverages the package's `setup.py` to execute malicious code during installation, or through module import. The objective is to gather basic system data, which could be a precursor to further compromise or credential theft.

Who's exposed

Profiles most at risk

  • Development teams using the pip ecosystem
  • CI/CD pipelines that pull unpinned dependencies or the latest versions of packages
  • Systems administrators or developers who manually install Python packages from PyPI

Conditions that increase exposure

  • Unpinned dependencies in `requirements.txt` or `pyproject.toml` that could resolve to the malicious version
  • Lack of dependency lockfiles (`Pipfile.lock`, `poetry.lock`)
  • Use of internal mirrors that have not synchronized with PyPI's removal of the malicious package
  • Direct or transitive dependency on 'dbt-sa-cli' version 0.0.1

Blast-radius scenarios

  • An attacker could gain basic host information (e.g., IP address, username) from compromised systems.
  • This exfiltrated data could be used for reconnaissance, leading to more targeted attacks or credential theft.
  • The blast radius includes any system where 'dbt-sa-cli' version 0.0.1 was installed or imported, potentially exposing development, testing, or production environments.

What to do (defensive)

Detect

  • Scan dependency trees for 'dbt-sa-cli' version 0.0.1.
  • Monitor network traffic for unusual outbound connections from systems where Python packages are installed or run.
  • Review `setup.py` files for suspicious commands or overrides in packages being installed.

Contain

  • Immediately remove 'dbt-sa-cli' version 0.0.1 from all environments.
  • Block 'dbt-sa-cli' version 0.0.1 from being downloaded from package registries or internal mirrors.
  • Isolate any systems identified as having installed the malicious package.

Remediate

  • Force-update all dependencies to known good versions, utilizing lockfiles.
  • Rotate credentials and API keys on any system that installed the malicious package.
  • Conduct a forensic analysis on affected systems to determine the full extent of data exfiltration and potential further compromise.

Frontier verdict — High

Prioritize immediate removal of 'dbt-sa-cli' v0.0.1 and credential rotation due to critical severity and host information exfiltration.

Sources

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