Which versions of localization-fixer are malicious?

The following npm versions of localization-fixer are flagged malicious: 1.0.1, 1.1.1. Treat any of these as compromised.

How do I remediate localization-fixer if I installed it?

Remove localization-fixer from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed localization-fixer — how do I know if it already compromised me?

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

Yes — localization-fixer is associated with the IN-MAL-2026-017195, IN-MAL-2026-017193 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 localization-fixer 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 localization-fixer (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging localization-fixer across your stack and pipelines.

Malicious package

localization-fixernpm

localization-fixer is a confirmed malicious npm package (MAL-2026-13631) that executes malicious code on install (malicious versions 1.0.1, 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in localization-fixer (npm)

MAL-2026-13631

Immediate action

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

npm uninstall localization-fixer

What this malware does

On require of the package's main entry, a top-level if (isServer) syncLanguageSystem() fetches a JSON payload from https://api.jsonbin.io/v3/b/6a764665da38895dfec7cd5d and executes the returned record.value field as JavaScript, both by writing it to a temp file and running it via child_process.fork and via new Function('require', payload)(require) in a separate module-load IIFE that pulls https://api.jsonbin.io/v3/b/6a718a58da38895dfeb6e2ed. Both sinks pass the Node require to the constructed function, granting full Node capabilities to whatever the mutable jsonbin.io bin currently serves. Function and variable names (syncLanguageSystem, LANG_SOURCE, lang_pass_key) frame the fetch-and-exec as a localization-sync feature, but the advertised purpose of the package has no need to evaluate remote bytes. The jsonbin.io bins are attacker-mutable, so the payload delivered to any installer is arbitrary and can change at any moment.

Malicious versions

2 flagged

1.0.11.1.1

Indicators of compromise (SHA-256)

72446c1307e81047c64d819d3485fa77062061c8c9d4d0b38b42e311137c8701

cce6487bd92f993e2f16873190e8e9f9fa5727509802c1db2a37e8be70c26343

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for localization-fixer (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging localization-fixer across your stack and pipelines.
If you installed it — respond
Remove localization-fixer from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If localization-fixer 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 localization-fixer 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. localization-fixer on npm has been identified as a malicious package (versions 1.0.1, 1.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017195IN-MAL-2026-017193

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks localization-fixer-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