Which versions of tyepescript-cli are malicious?

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

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

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

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

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

Malicious package

tyepescript-clinpm

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

MAL-2026-14143

Immediate action

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

npm uninstall tyepescript-cli

What this malware does

tyepescript-cli is a typosquat of typescript. Its scripts/postinstall.js XOR-decodes (key stf2026) a set of obfuscated byte arrays that resolve to an attacker-controlled URL, a PowerShell bridge command, and script fragments. On Windows, the postinstall downloads main.exe from github.com/bebrazi/qPbM50V1AKG0rVlH/releases/download/null/main.exe to %TEMP%\main.exe and spawns it detached. Under WSL, it decodes a powershell.exe bridge command and execs it via child_process.exec with windowsHide: true to fetch and run the same binary on the Windows host from the Linux install context. Before the drop, the script POSTs a JSON body with a host label to a hardcoded numeric IP http://193.70.34.101:20099/vote (host built by joining the array ['193','70','34','101'] to hide the literal) as an install-time beacon. The mutable releases/download/null/ path on an anonymous personal GitHub account (bebrazi) is unrelated to any legitimate typescript publisher, and the XOR obfuscation of URLs and commands has no benign purpose in an npm install script.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

8a867a5fc578cb6dcb759370e837d1a4c7e24f6db63c0c0f781e2c24995905e6

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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