Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malicious code in localization-fixer (npm)

The npm package localization-fixer contained malicious code that fetches and executes arbitrary JavaScript from attacker-controlled jsonbin.io endpoints on package require, granting full Node.js capabilities to remote payloads.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any developer or application that installed the malicious localization-fixer package and required it in their code.
Ecosystems
Attack vectors
Affected entities
  • localization-fixernpm package containing malicious code

The localization-fixer npm package contained embedded malicious code that executes on package initialization. When the package's main entry point is required, a top-level conditional check (if (isServer) syncLanguageSystem()) triggers a fetch from attacker-controlled jsonbin.io endpoints.\n\nThe malicious code retrieves JSON payloads from two separate jsonbin.io bins and executes the returned data as JavaScript through multiple execution paths: writing to a temporary file and executing via child_process.fork, and via new Function('require', payload)(require) in a separate module-load IIFE. Both execution methods pass the Node.js require function to the constructed code, granting full Node.js capabilities.\n\nThe functionality is disguised as a localization-sync feature through misleading function and variable names (syncLanguageSystem, LANG_SOURCE, lang_pass_key), but the package's advertised purpose has no legitimate need to evaluate remote code. Since the jsonbin.io bins are mutable by the attacker, the payload delivered to installers is arbitrary and can change at any moment, enabling dynamic malicious behavior.\n\nThe incident was identified and credited to the OpenSSF malicious-packages project.

Indicators of compromise

Packages
  • localization-fixer
Domains
  • api.jsonbin.io

Remediation

  • Immediately uninstall localization-fixer from all projects and dependencies
  • Audit all systems where localization-fixer was installed for signs of compromise or unauthorized access
  • Review npm audit logs and package-lock.json files to identify affected installations
  • Rotate any credentials or secrets that may have been exposed on systems running the malicious package
  • Update to a clean, verified version of any localization functionality from a trusted source
  • Consider implementing package integrity verification and supply chain security scanning in your build pipeline

Sources

  1. GitHub Advisory GHSA-744p-7qm5-8wpj · GitHub Advisory Database

Cite this entry

"Malicious code in localization-fixer (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 8, 2026; last updated August 8, 2026. https://supplychainattack.org/incident/malicious-code-in-localization-fixer-npm-1ncar9

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. resolvedcritical

    Malicious code in autbank-core (npm)

    The npm package autbank-core contained malicious preinstall and postinstall lifecycle hooks that exfiltrated environment variables, credentials, and system information to a hardcoded webhook.site endpoint during installation.

    npmCompromised package
  2. resolvedcritical

    Malicious code in adxaa (npm)

    The npm package adxaa contained obfuscated malicious JavaScript designed to target users of a specific WordPress site. The payload exfiltrates session data, deletes accounts, and hijacks credentials via email overwrite and password reset.

    npmCompromised package
  3. resolvedcritical

    Malicious code in upload-to-gcp (npm)

    upload-to-gcp@3.2.1 (npm) contains malicious code in its postinstall script that exfiltrates host identifiers to an attacker-controlled endpoint. The package masquerades as a Google Cloud Platform utility but performs unauthorized telemetry collection at install time.

    npmCompromised package
  4. resolvedcritical

    Malicious code in akamai-sensor (npm)

    A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.

    npmCompromised packageTyposquatting