Which versions of typescrip-cli are malicious?

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

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

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

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

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

Malicious package

typescrip-clinpm

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

MAL-2026-14150

Immediate action

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

npm uninstall typescrip-cli

What this malware does

Package name 'typescrip-cli' typosquats 'typescript-cli'; index.js exports an empty object and the package has no library functionality. scripts/postinstall.js hides its network destinations and command lines inside four numeric byte arrays that are XOR-decoded at runtime with the key 'stf2026'. The decoded URL is https://github.com/bebra1/qPzM50V1AKG0rVlH/releases/download/null/main.exe (an unrelated personal GitHub account, mutable 'null' release tag). On Windows the script downloads that executable to %TEMP%\main.exe and spawns it detached. On WSL/virtualized Linux it decodes a PowerShell launcher and bridge script and passes the concatenated command to child_process.exec with windowsHide:true, running the same payload on the Windows host across the WSL boundary. In parallel, postinstall POSTs a JSON body identifying the host platform to a hardcoded bare-IP beacon at http://193.70.34.101:20099/vote, with the host string reassembled from a split array ['193','70','34','101'].join('.') to avoid literal-string detection.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

44399cd197dfa6f24adf7c96a380d2e0c95a4123d8c14932ceb0a85e32ebc9b9

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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