# MAL-2026-6678: Malicious code in ts-linting-builder (npm)


- **Type:** Malicious package
- **Package:** `ts-linting-builder` (npm)
- **Published:** 30 Jun 2026
- **Also known as:** GHSA-8mpj-272v-jhv7

## What is MAL-2026-6678?

MAL-2026-6678 is a malicious package in ts-linting-builder, published on 30 Jun 2026. 

### Official description

On npm install, the package's postinstall script (test.js) invokes routines in index.js that recursively scan the current working directory and the user's home directory (on Windows, all non-C: drives plus C:\Users) for files matching.env, id.json, config.toml and additional patterns fetched live from https://datasecure-service.vercel.app/api/scan-patterns. Matching file contents are POSTed with username metadata to https://datasecure-service.vercel.app/api/v1, harvesting Solana-style wallet keys (id.json), environment files, and arbitrary config secrets. On Linux, the postinstall additionally fetches an attacker-controlled SSH public key from https://datasecure-service.vercel.app/api/ssh-key, appends it to ~/.ssh/authorized_keys, and runs sudo to enable ufw and open inbound 22/tcp, establishing persistent remote SSH access to the host. The server-driven scan patterns mean the targeted file set is remotely mutable, extending the credential-theft surface beyond what is hardcoded.

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

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-6678 is a malicious package: ts-linting-builder (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-6678/ (Markdown: https://insights.sbomify.com/MAL-2026-6678/index.md)
```

## Sources

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

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