Which versions of typescipt-core are malicious?

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

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

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

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

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

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

Malicious package

typescipt-corenpm

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

MAL-2026-14147

Immediate action

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

npm uninstall typescipt-core

What this malware does

Package name typosquats typescript. The postinstall script (scripts/postinstall.js) XOR-decodes a download URL and a PowerShell launcher using key 'stf2026', then on Windows fetches an executable to %TEMP%\main.exe and spawns it detached; on WSL it decodes and executes a PowerShell bridge via exec. Before fetching the second stage, it POSTs a host-profile JSON (including a Windows/WSL label derived from inspecting /proc/version and /proc/sys/kernel/osrelease) over plain HTTP to the hardcoded bare IP 193.70.34.101 on port 20099 at path /vote. The network destinations and shell command are stored as XOR-encoded byte arrays (ADDON_ENC, BRIDGE_LAUNCHER_ENC, BRIDGE_SCRIPT_PRE_ENC, BRIDGE_SCRIPT_POST_ENC) and reconstructed at runtime. Cover-story identifiers ('TELEMETRY', 'addon') mask an install-time dropper: npm install typescipt-core results in attacker-controlled code executing on the installer's host.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

98b97af3a328b837904c7860b7acbae33bea28afb53949905868867905c14be6

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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