Which versions of typscript-cli are malicious?

The following npm versions of typscript-cli are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate typscript-cli if I installed it?

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

I already installed typscript-cli — how do I know if it already compromised me?

If typscript-cli 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 typscript-cli part of a known attack campaign?

Yes — typscript-cli is associated with the IN-MAL-2026-018193 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 typscript-cli 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 typscript-cli (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging typscript-cli across your stack and pipelines.

Malicious package

typscript-clinpm

typscript-cli is a confirmed malicious npm package (MAL-2026-14156) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in typscript-cli (npm)

MAL-2026-14156

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall typscript-cli

What this malware does

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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

1425e6f0bb2305eeddecaab5403e09ead0e8f60b9b1f817581a343cb5a3dd062

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 typscript-cli (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging typscript-cli across your stack and pipelines.
If you installed it — respond
typscript-cli is a typosquat — you almost certainly intended a legitimately-named package. Remove typscript-cli, 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 typscript-cli 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 typscript-cli 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. typscript-cli on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018193

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks typscript-cli-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

Explore

All malware advisories How O3 detects malware Vulnerability database