Malicious Code in i18next-ext (npm)

i18next-ext Updated 02 Oct 2025

Summary

24/10/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8397: Malicious code in i18next-ext (npm). Affects i18next-ext versions 1.6.0. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The i18next-ext package is an npm package used for internationalization in JavaScript applications. It provides extensions and utilities for the i18next library, allowing developers to easily implement multi-language support in their applications. However, the package has been identified as malicious by the OpenSSF Package Analysis project.

Vulnerability Detail

The i18next-ext package has been flagged as malicious because it communicates with a domain associated with malicious activity. This indicates that the package may be performing unauthorized actions or collecting sensitive information from the user's environment. The specific ramifications of this vulnerability may vary depending on the intentions of the malicious code, but it could potentially lead to data breaches, unauthorized access, or other security issues.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall i18next-ext

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no known workaround for this vulnerability. It is crucial to remove the i18next-ext package and replace it with a trusted alternative to ensure the security of your application.

Conclusion

The i18next-ext package has been identified as malicious and should be removed from your project to ensure the security of your application. It is recommended to replace it with a trusted alternative and regularly update your dependencies. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for i18next-ext →

Share this vulnerability

FAQ

i18next-ext is an npm package used for internationalization in JavaScript applications. It provides extensions and utilities for the i18next library.

The i18next-ext package has been flagged as malicious because it communicates with a domain associated with malicious activity, indicating potential unauthorized actions or data collection.

The specific ramifications may vary, but they could include data breaches, unauthorized access, or other security issues.

To fix this vulnerability, remove the i18next-ext package from your project and replace it with a trusted alternative. Regularly update your dependencies and use vulnerability monitoring tools like Vulert.

No, there is no known workaround. It is crucial to remove the i18next-ext package and replace it with a trusted alternative.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall i18next-ext

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback