# MAL-2026-15934: Malicious code in dbt-sa-cli (PyPI)


- **Type:** Malicious package
- **Package:** `dbt-sa-cli` (PyPI)
- **Published:** 5 Sep 2026

## What is MAL-2026-15934?

MAL-2026-15934 is a malicious package in dbt-sa-cli, published on 5 Sep 2026. 

### Official description

setup.py defines rce_poc() and invokes it at module top level, so the code runs unconditionally during `pip install dbt-sa-cli`. The function collects installer-side identifiers (hostname, USER/USERNAME, current working directory, home path) and sends them out-of-band via a DNS lookup to a subdomain of yokodnssmamqdchvjfyqyo8zaq3s90h8e.oast.fun and an HTTPS POST to https://yokodnssmamqdchvjfyqyo8zaq3s90h8e.oast.fun/dbt-sa-cli. The same install-time path drops a marker file at ~/.dbt-sa-cli-rce-poc in the installer's home directory, demonstrating arbitrary code execution during install. The package name resembles the dbt ecosystem, making this a typosquat lure. Regardless of any 'security research' framing, installing the package produces immediate installer-side data disclosure and code execution against an author-controlled OOB collector.

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-15934?

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-15934 is a malicious package: dbt-sa-cli (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-15934/ (Markdown: https://insights.sbomify.com/MAL-2026-15934/index.md)
```

## Sources

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

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