# MAL-2026-6367: Malicious code in dbt-language-server (npm)


- **Type:** Malicious package
- **Package:** `dbt-language-server` (npm)
- **Published:** 24 Jun 2026
- **Also known as:** GHSA-w54g-2v55-m5vr

## What is MAL-2026-6367?

MAL-2026-6367 is a malicious package in dbt-language-server, published on 24 Jun 2026. 

### Official description

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.

## What should I do about MAL-2026-6367?

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

## Sources

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

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