Which versions of dbt-language-server are malicious?

The following npm versions of dbt-language-server are flagged malicious: 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate dbt-language-server if I installed it?

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

If dbt-language-server was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is dbt-language-server part of a known attack campaign?

Yes — dbt-language-server is associated with the IN-MAL-2026-007419, GHSA-w54g-2v55-m5vr, IN-MAL-2026-019772 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-language-server across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dbt-language-server (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dbt-language-server across your stack and pipelines.

Malicious package

dbt-language-servernpm

dbt-language-server is a confirmed malicious npm package (MAL-2026-6367) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dbt-language-server (npm)

MAL-2026-6367

Immediate action

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

npm uninstall dbt-language-server

What this malware does

package.json declares a preinstall hook (node index.js) that runs automatically on npm install. index.js collects installer-side reconnaissance data — hostname, username, home directory, DNS servers, package metadata — and reads the contents of /etc/passwd and /etc/hosts from the installer machine, then POSTs the bundle over HTTPS to p9z268f2xv8co3wtlpujplris9y2msah.oastify.com, a Burp Collaborator subdomain used for out-of-band exfiltration. The package has empty author/description/license fields and ships no functionality beyond this payload. The name dbt-language-server shadows a plausible internal/private package, consistent with a dependency-confusion attack targeting organizations that use a dbt-related internal tool.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged

1.0.11.0.2

Indicators of compromise (SHA-256)

b15387169de77b4c18baf8c3f4d27156085bd06d96d0a27879545c3f0358dba8

931bd59f8c8d003669ac94aa3d0d3f2f9367801434dc8770c0c4efce80d412a6

4025f55aaa823f375775803257ebc5262918b00108f49539a76e378f15cd50e8

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dbt-language-server (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dbt-language-server across your stack and pipelines.
If you installed it — respond
dbt-language-server 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-language-server was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks dbt-language-server before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. dbt-language-server on npm has been identified as a malicious package (versions 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007419GHSA-w54g-2v55-m5vrIN-MAL-2026-019772

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dbt-language-server-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