# MAL-2026-10980: Malicious code in nolby (npm)


- **Type:** Malicious package
- **Package:** `nolby` (npm)
- **Published:** 21 Jul 2026
- **Also known as:** GHSA-x724-q7wp-wx6q

## What is MAL-2026-10980?

MAL-2026-10980 is a malicious package in nolby, published on 21 Jul 2026. 

### Official description

The package advertises itself as a pure calendar/streak math library with no import-time side effects, but index.mjs invokes a top-level `_sync()` on module load. When loaded on a Linux process with access to `/mnt/c` (a WSL environment), the function enumerates Windows user profiles under `/mnt/c/Users` and writes the bundled `cache.dat` bytes to `AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\vite-native-helper.exe` under the first user's profile. The shipped `cache.dat` is a Windows PE executable (contains the `!This program cannot be run in DOS mode` stub and standard PE sections `.rdata`, `.pdata`, `.reloc`); it is declared in the `files` array as opaque data and renamed at write time to a Vite-lookalike filename. Placement in the Startup folder causes the PE to execute on the Windows user's next login, establishing persistent code execution on the WSL host's Windows side triggered by a normal `require`/`import` of the package.

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

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

## Sources

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

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