Which versions of typesript-cli are malicious?

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

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

typesript-cli establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

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

Yes — typesript-cli is associated with the IN-MAL-2026-018192 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 typesript-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 typesript-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 typesript-cli across your stack and pipelines.

Malicious package

typesript-clinpm

typesript-cli is a confirmed malicious npm package (MAL-2026-14154) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in typesript-cli (npm)

MAL-2026-14154

Immediate action

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

npm uninstall typesript-cli

What this malware does

Package name is a one-character typosquat of the widely-used 'typescript' family. On npm install, scripts/postinstall.js XOR-decodes (key 'stf2026') a GitHub-hosted URL held as an integer array and downloads a Windows PE to TEMP\main.exe, then spawns it detached with no hash or signature verification. When running under WSL or virtualized Linux (detected via /proc/version and WSLENV), the script decodes a bridge launcher command and inline script from further XOR-obfuscated blobs and executes them via child_process.exec with windowsHide:true to fetch and run the same payload on the Windows host, crossing the Linux sandbox boundary. The script also POSTs platform info to a hardcoded bare-IP endpoint http://193.70.34.101:20099/vote, with the IP split across a string array ['193','70','34','101'].join('.') to hide it from static review, serving as an install beacon.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

3ac32bb6c3db806740bda125cf58a8f348256baa021b0a6c7b901ebb86720505

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for typesript-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 typesript-cli across your stack and pipelines.
If you installed it — respond
typesript-cli establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If typesript-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 typesript-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. typesript-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-018192

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks typesript-cli-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database