# MAL-2026-6937: Malicious code in nuxt-fonts-devtools (npm)


- **Type:** Malicious package
- **Package:** `nuxt-fonts-devtools` (npm)
- **Published:** 7 Jul 2026
- **Also known as:** GHSA-hw4h-mjrw-4qv9

## What is MAL-2026-6937?

MAL-2026-6937 is a malicious package in nuxt-fonts-devtools, published on 7 Jul 2026. 

### Official description

Package ships only a package.json and a readme; there is no main entry, no bin, no scripts, no dependencies, and no executable code. The readme contains the string 'Takeover By lobo' and the package.json description self-labels as a 'Security research canary — vercel'. Installing this version does not execute code and does not exfiltrate data, run remote payloads, or modify the installer's environment. However, the name resembles a Nuxt/Vercel devtools-adjacent package and the readme text asserts a namespace takeover, so the package is a name-squat placeholder rather than a functional library. Downstream consumers who add this dependency expecting real functionality will pull an empty package and, if the name is ever transferred or republished, could later receive attacker-controlled content under the same name.

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

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-6937 is a malicious package: nuxt-fonts-devtools (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-6937/ (Markdown: https://insights.sbomify.com/MAL-2026-6937/index.md)
```

## Sources

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

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