Malicious code in @tpci/i18next-ext (npm)

@tpci/i18next-ext Updated 02 Oct 2025

Summary

24/10/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8398: Malicious code in @tpci/i18next-ext (npm). Affects @tpci/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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @tpci/i18next-ext package is an npm package that extends the functionality of the i18next library. It provides additional features and utilities for internationalization in JavaScript applications. The package is widely used in various projects that require multi-language support. However, version 1.6.0 of the package has been identified as malicious by the OpenSSF Package Analysis project.

Vulnerability Detail

The identified version of @tpci/i18next-ext (1.6.0) has been flagged as malicious due to its communication with a domain associated with malicious activity. This indicates that the package may be involved in unauthorized or harmful activities within the application environment. The presence of malicious code in the package poses a significant risk to the security and integrity of the affected applications. It is crucial to address this vulnerability promptly to prevent potential data breaches, unauthorized access, or other malicious activities.

How To Fix

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

npm uninstall @tpci/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 specific workaround mentioned for this vulnerability. The recommended course of action is to follow the steps mentioned in the 'how_to_fix' section and remove or update the package to a non-malicious version.

Conclusion

The @tpci/i18next-ext package version 1.6.0 has been identified as malicious and should be promptly removed or updated to a non-malicious version. This vulnerability poses a significant risk to the security and integrity of affected applications. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for @tpci/i18next-ext →

Share this vulnerability

FAQ

@tpci/i18next-ext is an npm package that extends the functionality of the i18next library for internationalization in JavaScript applications.

This vulnerability can lead to unauthorized access, data breaches, or other malicious activities within the affected application environment.

To fix this vulnerability, you should remove or update the @tpci/i18next-ext package to a non-malicious version and scan the application codebase for any traces of the malicious code.

It is recommended to check for the latest version of the @tpci/i18next-ext package and any associated security advisories or patches.

Regularly monitoring and updating dependencies, as well as conducting security audits, can help prevent similar vulnerabilities in the future.

How To Fix

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

npm uninstall @tpci/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