Which versions of typscript-core are malicious?

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

How do I remediate typscript-core if I installed it?

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

I already installed typscript-core — how do I know if it already compromised me?

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

Yes — typscript-core is associated with the IN-MAL-2026-018194 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 typscript-core 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 typscript-core (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 typscript-core across your stack and pipelines.

Malicious package

typscript-corenpm

typscript-core is a confirmed malicious npm package (MAL-2026-14157) 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 typscript-core (npm)

MAL-2026-14157

Immediate action

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

npm uninstall typscript-core

What this malware does

typscript-core is a typosquat of the 'typescript' package. Its scripts/postinstall.js reconstructs a GitHub download URL and shell commands from byte arrays XOR-decoded with the key 'stf2026', downloads a binary to %TEMP%\main.exe, and spawns it detached with windowsHide:true on win32 (and via a PowerShell bridge on WSL). The same postinstall also POSTs platform information to a hardcoded bare-IP endpoint at http://193.70.34.101:20099/vote, with the IP assembled from a four-element string array to evade static search. The URLs, shell commands, and destination IP are all obfuscated and reconstructed at runtime.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

5120bfde64344d0e161bac3b4128d7eeecc483ad796361db09eacd138ecd3945

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 typscript-core (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 typscript-core across your stack and pipelines.
If you installed it — respond
typscript-core is a typosquat — you almost certainly intended a legitimately-named package. Remove typscript-core, 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 typscript-core 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 typscript-core 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. typscript-core 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-018194

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks typscript-core-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