Which versions of typescirpt-cli are malicious?

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

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

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

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

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

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

Malicious package

typescirpt-clinpm

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

MAL-2026-14148

Immediate action

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

npm uninstall typescirpt-cli

What this malware does

The package's postinstall script (scripts/postinstall.js) XOR-decodes obfuscated byte arrays using the key 'stf2026' to reconstruct a download URL and a powershell command. On Windows, and on Linux when WSL is detected, it downloads an opaque main.exe from https://github.com/bebraz1/qPzM50V1AKG0rVlH/releases/download/null/main.exe (an unrelated personal GitHub account, no version tag, no hash/signature verification) into TEMP and spawns it detached; from WSL it invokes a decoded powershell.exe bridge to fetch and run the binary on the Windows host. Separately, sendInstallMetrics POSTs a JSON payload containing node/arch/platform to the hardcoded bare IP 193.70.34.101:20099/vote over plain HTTP, with the host reconstructed via array-join to obscure the literal. The package name typosquats 'typescript-cli'.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

09d82fa51e42e6766fe0819517e9fb5be633702a0e22cb4da05d8920cb413c53

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 typescirpt-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 typescirpt-cli across your stack and pipelines.
If you installed it — respond
typescirpt-cli is a typosquat — you almost certainly intended a legitimately-named package. Remove typescirpt-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 typescirpt-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 typescirpt-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. typescirpt-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-018186

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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