Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
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
  1. Find it

    Search your lockfiles and build artifacts for typescriptt-cli (version 1.0.0).

  2. 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.

  3. Did it already run?

    If typescriptt-cli was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

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.

Explore

typescriptt-cli (npm) malicious package — MAL-2026-14151 | O3 Security