Which versions of typescrit-cli are malicious?

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

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

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

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

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

Malicious package

typescrit-clinpm

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

MAL-2026-14153

Immediate action

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

npm uninstall typescrit-cli

What this malware does

On npm install, scripts/postinstall.js XOR-decodes (key 'stf2026') a hidden URL that resolves to an unrelated personal GitHub account (github.com/bebra1/...), downloads a payload to %TEMP%\main.exe, and spawns it detached with stdio ignored and window hidden. When the host is detected as WSL (via /proc/version, /proc/sys/kernel/osrelease, WSL_DISTRO_NAME), the script assembles an XOR-decoded powershell.exe bridge command and exec()s it to escape the Linux container and run the same payload on the Windows host. The same postinstall also POSTs a JSON body containing the platform to a hardcoded bare-IP C2 at http://193.70.34.101:20099/vote, with the IP assembled from a split array (['193','70','34','101'].join('.')) to evade literal-URL detection. All network destinations and shell command fragments (addon URL, powershell launcher, bridge script fragments) are stored as byte arrays and XOR-decoded at runtime. The package name resembles a mistyped 'typescript-cli' and the publisher is unrelated to the GitHub account hosting the payload.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

adcb90c6a48b3b20928967d1aea32cde54035ed455c474a6db4fab148b424b53

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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