Malicious code in require-i18next (npm)
The npm package require-i18next version 20.0.0 was identified as malicious by the OpenSSF Package Analysis project. The package communicates with domains associated with malicious activity and executes commands associated with malicious behavior.
- Disclosed
- Last updated
- Blast radius
- All npm users who installed require-i18next version 20.0.0
- Ecosystems
- Attack vectors
- Affected entities
- require-i18next · 20.0.0
The OpenSSF Package Analysis project identified require-i18next version 20.0.0 on npm as containing malicious code. The analysis determined that the package exhibits two key indicators of compromise: it communicates with a domain associated with malicious activity, and it executes one or more commands associated with malicious behavior.\n\nThis finding was published on GitHub's advisory database (GHSA-4m9p-v3v7-c5xh) and credited to the OpenSSF malicious-packages repository. The malicious package was identified through automated analysis of package behavior.\n\nUsers who installed this specific version are at risk of compromise through command execution and potential data exfiltration via the malicious domain communications.
Indicators of compromise
- Packages
- require-i18next@20.0.0
Remediation
- Immediately remove require-i18next version 20.0.0 from all environments
- Audit systems that may have executed this package for signs of compromise
- Review network logs for connections to the malicious domain identified in the analysis
- Update to a safe version of require-i18next if available, or use an alternative package
- Check npm audit reports and dependency trees for this package across your projects
Sources
- GitHub Advisory GHSA-4m9p-v3v7-c5xh · GitHub Advisory Database
Cite this entry
"Malicious code in require-i18next (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 15, 2026; last updated August 15, 2026. https://supplychainattack.org/incident/malicious-code-in-require-i18next-npm-1a054w
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in 3-buildsight-web (npm)
The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.
npmCompromised package - resolvedcritical
Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)
Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.
npmDependency confusionCompromised package - resolvedcritical
Malicious code in create-coin (npm)
create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.
npmCompromised packageTyposquatting - resolvedcritical
Malicious code in @syncraft-labs/vue (npm)
The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.
npmCompromised package