Which versions of typescipt-cli are malicious?

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

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

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

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

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

Malicious package

typescipt-clinpm

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

MAL-2026-14146

Immediate action

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

npm uninstall typescipt-cli

What this malware does

Package name typosquats 'typescript'. scripts/postinstall.js runs at npm install time and: (1) POSTs a JSON body with the installer's platform label to 193.70.34.101:20099/vote, with the IP split into a string array ['193','70','34','101'].join('.') to obscure it; (2) XOR-decodes a hardcoded URL (github.com/bebraz1/qPzM50V1AKG0rVlH/releases/download/null/main.exe) using key 'stf2026' via a byte-array unpackSegment helper, downloads the resulting binary to %TEMP%\main.exe on Windows, and launches it detached with windowsHide; (3) on WSL, XOR-decodes a PowerShell bridge command and exec's it to run the same download on the host Windows. No hash or signature verification. URLs, commands, and the C2 IP are stored as encoded byte arrays and reconstructed at runtime.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

b080f58ace02e860729134afd887943345248628e5c201a5fd2e46c71f439d29

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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