Which versions of typecript-cli are malicious?

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

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

typecript-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 typecript-cli — how do I know if it already compromised me?

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

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

Malicious package

typecript-clinpm

typecript-cli is a confirmed malicious npm package (MAL-2026-14145) 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 typecript-cli (npm)

MAL-2026-14145

Immediate action

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

npm uninstall typecript-cli

What this malware does

[email protected] is a typosquat of 'typescript' whose scripts/postinstall.js performs an install-time dropper attack. Payload strings are stored as integer arrays and XOR-decoded at runtime with key 'stf2026' via an unpackSegment() helper, hiding the download URL and PowerShell command from static scanners. On Windows hosts, the script downloads main.exe from https://github.com/bebraz1/<repo>/releases/download/<tag>/main.exe (a personal GitHub account unrelated to the package publisher) to %TEMP%/main.exe, then spawns it detached with no hash or signature verification. When running under WSL, the script uses an exec() bridge that invokes powershell.exe on the Windows host to escape the Linux install sandbox and execute the same payload. Postinstall also POSTs a JSON body with the resolved platform label to a hardcoded bare-IP endpoint at http://193.70.34.101:20099/vote, with the IP assembled from a split octet array (['193','70','34','101'].join('.')) to evade string matching, serving as an install beacon and host selector.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

03604fc37a8607bf5c14f409dc9d13308bff3e7ec145de955ae13a07c13da92e

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 typecript-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 typecript-cli across your stack and pipelines.
If you installed it — respond
typecript-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 typecript-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 typecript-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. typecript-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-018183

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks typecript-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