# MAL-2026-15564: Malicious code in vs-modules (npm)


- **Type:** Malicious package
- **Package:** `vs-modules` (npm)
- **Published:** 29 Aug 2026
- **Also known as:** GHSA-8hpw-v4hq-pg99

## What is MAL-2026-15564?

MAL-2026-15564 is a malicious package in vs-modules, published on 29 Aug 2026. 

### Official description

package.json declares a preinstall hook that runs `node resources.js`, which fires automatically on `npm install`. resources.js is heavily obfuscated with an obfuscator.io-style string-array plus numeric-index dispatch that hides the URL, destination path, and exec call. Deobfuscation shows the script reconstructs the plain-HTTP URL http://whaomydaddy.bts-the-time-in-shanghai.netlify.app/hey.bat, downloads it into %TEMP% via `curl -L -o <dest> <url>`, and immediately runs the batch file via child_process.exec. The destination is an anonymous netlify subdomain over plain HTTP with no pinning or integrity check, so any content served at that URL executes on the installer's host at install time. The package's stated purpose (a kanban/utility module) is unrelated to fetching and executing a Windows batch file from an external host.

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

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

## Sources

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

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