# MAL-2026-15664: Malicious code in @yane88/workbuddy (npm)


- **Type:** Malicious package
- **Package:** `@yane88/workbuddy` (npm)
- **Published:** 1 Sep 2026
- **Also known as:** GHSA-v22h-4j6c-58cm

## What is MAL-2026-15664?

MAL-2026-15664 is a malicious package in @yane88/workbuddy, published on 1 Sep 2026. 

### Official description

At npm install time, @yane88/workbuddy@1.0.1's postinstall script pulls three sibling npm packages (@yane88/workbuddy-01, -02, -03), each shipping a PKWARE split-zip volume (.z01/.z02/.zip), concatenates them into a multi-volume ZIP, inflates the contents, and writes WorkBuddy-5.3.5.exe into the package directory with chmod applied. The payload bytes are distributed across separate npm packages rather than shipped in this package's own tarball, there is no hash or signature verification of the reassembled archive, and no README or metadata describes what the executable does or why splitting across packages is necessary. Splitting a Windows PE across multiple sibling packages and reassembling it at install time is a delivery/staging pattern for opaque binary payloads and is not a standard native-addon or prebuild-install workflow.

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

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

## Sources

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

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