Which versions of dbt-sa-cli are malicious?

The following PyPI versions of dbt-sa-cli are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate dbt-sa-cli if I installed it?

dbt-sa-cli 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 dbt-sa-cli — how do I know if it already compromised me?

If dbt-sa-cli 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 dbt-sa-cli part of a known attack campaign?

Yes — dbt-sa-cli is associated with the GENERIC-standard-pypi-install-pentest, IN-MAL-2026-019649 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 dbt-sa-cli across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dbt-sa-cli (version 0.0.1).

Malicious package

dbt-sa-cliPyPI

Advisory published Sep 5, 2026Updated Sep 6, 2026

dbt-sa-cli is a confirmed malicious PyPI package (MAL-2026-15934) that steals credentials and exfiltrates sensitive data (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dbt-sa-cli (PyPI)

MAL-2026-15934

Immediate action

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

pip uninstall dbt-sa-cli

What this malware does

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.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

23702c2370cf8873f90f85f178de5d781c9244f91fe412c952fc3cca8e98f974

9a3fc52d1baa65bd51dd9659641f0df237ea2a595358cd91b19fd8988ba3236a

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for dbt-sa-cli (version 0.0.1).
If you installed it — respond
dbt-sa-cli 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 dbt-sa-cli 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. dbt-sa-cli on PyPI has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-standard-pypi-install-pentestIN-MAL-2026-019649

References

Credits

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

Detect & block this

O3 blocks dbt-sa-cli-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