typscript-cli
Affected
- Versions:
1.0.0
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in typscript-cli (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (1425e6f0bb2305eeddecaab5403e09ead0e8f60b9b1f817581a343cb5a3dd062)
typscript-cli is a typosquat of 'typescript' (index.js exports an empty object; no library functionality). Its scripts/postinstall.js is the only functional code and executes on npm install. It XOR-decodes (key 'stf2026') four embedded numeric arrays to reconstruct a download URL and a PowerShell 'bridge' command, downloads a Windows executable to %TEMP%\main.exe, and spawns it detached with windowsHide:true. On WSL/Linux hosts it uses child_process.exec with the XOR-decoded PowerShell bridge command to drop and run the same payload on the Windows side. The same postinstall also POSTs a platform label to a hardcoded bare-IP endpoint 193.70.34.101:20099/vote over plain HTTP, with the host assembled from a split array ['193','70','34','101'].join('.') to evade literal-string scanning. There is no publisher-matched destination, no version pinning, and no integrity check on the fetched binary.
Not rated by the source.
1.0.0None 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