Which versions of typescriptt-cli are malicious?

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

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

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

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

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

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

Malicious package

typescriptt-clinpm

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

MAL-2026-14151

Immediate action

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

npm uninstall typescriptt-cli

What this malware does

typescriptt-cli is a typosquat of typescript-cli whose index.js is an empty module; its only real behavior is in scripts/postinstall.js. On npm install, the postinstall script XOR-decodes a hardcoded byte array with key 'stf2026' to reconstruct a URL pointing at github.com/bebraz1/qPzM50V1AKG0rVlH/releases/download/null/main.exe, downloads that Windows executable to %TEMP%\main.exe, and spawns it detached with windowsHide:true and stdio:'ignore'. When the host is WSL (detected by scanning /proc/version and /proc/sys/kernel/osrelease for 'microsoft'), the script assembles a powershell.exe command from three additional XOR-obfuscated byte arrays and passes it to child_process.exec to fetch and run the same binary on the Windows host, breaking out of the WSL boundary. Before the drop, the script POSTs a JSON platform label to a hardcoded bare-IP install-tracking endpoint at http://193.70.34.101:20099/vote. The download URL uses a personal GitHub account with the release tag literally 'null', no hash or signature verification is performed, and the executable payload is opaque.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

023f754538f603fbb5379ee8be82cb9524f710495e5dddc4e631e5aafbf323b5

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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