Critical Malicious Code Vulnerability in i18never Package

i18never Updated 16 Dec 2025

Summary

16/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192591: Malicious code in i18never (npm). Affected versions are not published. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The i18never package is an npm library designed for internationalization (i18n) in JavaScript applications. It provides developers with tools to manage translations and localization efficiently. However, it has been identified as containing malicious code that compromises the security of any system where it is installed.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the i18never package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications are severe, as it may lead to data breaches and loss of control over the affected systems. Users should be aware that simply removing the package may not eliminate all traces of the malicious software.

How To Fix

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

npm uninstall i18never

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

As a workaround, ensure that the i18never package is uninstalled from your project by running: npm uninstall i18never. However, be aware that this action may not fully mitigate the risks associated with the malicious code already executed on the system.

Conclusion

The i18never package has been identified as containing malicious code that poses a significant security risk. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for i18never →

Share this vulnerability

FAQ

i18never is an npm package used for internationalization in JavaScript applications, helping developers manage translations and localization.

The malicious code can compromise your system, allowing unauthorized access to sensitive information and potentially leading to data breaches.

You should immediately uninstall the i18never package and rotate any secrets or keys stored on the affected system.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Not necessarily. While removing the package is essential, there may still be remnants of the malicious code that could compromise your system.

How To Fix

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

npm uninstall i18never

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