# MAL-2026-15562: Malicious code in test-in-one (npm)


- **Type:** Malicious package
- **Package:** `test-in-one` (npm)
- **Published:** 29 Aug 2026

## What is MAL-2026-15562?

MAL-2026-15562 is a malicious package in test-in-one, published on 29 Aug 2026. 

### Official description

The package declares a local file: dependency (`detector` at `file:.yalc/detector`) whose `postinstall` script (`src/scripts/check.js`) executes automatically on `npm install`. The script walks the installer's home directory, Desktop, Documents, Projects, and cwd to harvest desktop crypto-wallet directories, browser extension LevelDB stores (MetaMask, Phantom, and similar), `~/.ssh/*` private keys, `~/.aws/credentials`, `~/.git-credentials`, `.env*`, `.npmrc`/`.yarnrc`, and the full `process.env`. The collected files are tarred and POSTed to a hardcoded Telegram Bot API endpoint (`https://api.telegram.org/bot<redacted>/sendDocument`, chat_id 416517694). The script additionally contains npm worm scaffolding: after collecting an npm token it calls `whoami` against `registry.npmjs.org`, enumerates all packages owned by the maintainer via the registry search API, and for each package downloads the tarball, injects a postinstall hook, bumps the version, writes a `.npmrc` with the stolen token, and prepares publication (the final publish call is currently gated by `if (false)`, but token theft, maintainer enumeration, and the injector pipeline are live). Bundling the payload as a `file:` dependency causes npm to install and run its lifecycle hooks without a registry fetch, making the manifest itself the delivery vector.

## What should I do about MAL-2026-15562?

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

## Sources

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

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