Critical Malicious Code Vulnerability in lang-codes Package

lang-codes Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191122: Malicious code in lang-codes (npm). Affects lang-codes versions 1.0.1 – 1.0.2. 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 lang-codes package is an npm library designed to provide a comprehensive list of language codes for developers. It is commonly used in applications that require localization or internationalization features. However, this package has been identified as containing malicious code, which poses significant security risks to any system that has it installed.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the lang-codes package, specifically in versions 1.0.1 and 1.0.2. This malicious code can compromise the entire system, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to the package being flagged by the GitHub Security Advisory (GHSA) as a malware threat, indicating that any system running this package should be considered fully compromised.

How To Fix

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

npm uninstall lang-codes

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 are no effective workarounds for this vulnerability other than removing the package entirely. It is essential to monitor your system for any signs of compromise after the removal.

Conclusion

The lang-codes package has been identified as containing malicious code that can compromise systems. Immediate action is required to remove the package and secure any sensitive information. Regular monitoring of dependencies is essential to prevent similar vulnerabilities in the future.

See every vulnerability recorded for lang-codes →

Share this vulnerability

FAQ

You should uninstall the lang-codes package immediately and rotate any sensitive information stored on your system.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Keeping the lang-codes package installed can lead to unauthorized access to your system, potentially compromising sensitive data and allowing malicious actors to control your environment.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities.

If immediate removal is not possible, ensure to isolate the affected system from the network and monitor for any suspicious activity until you can safely remove the package.

How To Fix

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

npm uninstall lang-codes

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