Which versions of localize-extract are malicious?

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

How do I remediate localize-extract if I installed it?

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

I already installed localize-extract — how do I know if it already compromised me?

If localize-extract 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.

Is localize-extract part of a known attack campaign?

Yes — localize-extract is associated with the IN-MAL-2026-018362 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 localize-extract across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for localize-extract (version 1.0.0).

Malicious package

localize-extractnpm

Advisory published Aug 19, 2026Updated Aug 19, 2026

localize-extract is a confirmed malicious npm package (MAL-2026-14249) 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 localize-extract (npm)

MAL-2026-14249

Immediate action

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

npm uninstall localize-extract

What this malware does

[email protected] executes a postinstall script that collects host identifiers (os.hostname(), platform, arch, node version, package name, lifecycle event) and POSTs them as JSON to the hardcoded endpoint https://1zrgq9h2.instances.poc.jchunt.top/localize-extract at npm install time. The package name resembles @angular/localize and the tarball references the upstream angular/localize package.json, consistent with a dependency-confusion / typosquat probe. Data leaves the installer's machine to an attacker-chosen host without consent on install.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

265d3f1cc9dae0e1599e17054e0cebe1481224741d3c3dce5d78916feebd5da2

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for localize-extract (version 1.0.0).
If you installed it — respond
localize-extract is a typosquat — you almost certainly intended a legitimately-named package. Remove localize-extract, 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 localize-extract 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. localize-extract 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-018362

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks localize-extract-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