require-i18next (npm) · Malicious Code
Affects require-i18nextSource GCVE Database
Malicious package : remove require-i18next and rotate any secrets on hosts that installed it.
Data as of 26 Oct 2026, 16:17 UTC
Malicious package
Published to npm · OSV MAL-2026-14052
What to do
Remove require-i18next from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmrequire-i18next | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: ossf-package-analysis (6ea984228059ea2f54b4cb42d16a5f3f42f3144902c418be08c5000576de58f1) The OpenSSF Package Analysis project identified 'require-i18next' @ 20.0.0 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.