Critical Malicious Code Vulnerability in crypto-locale Package

crypto-locale Updated 20 Feb 2026

Summary

20/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-955: Malicious code in crypto-locale (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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The crypto-locale package is an npm library designed to provide locale-specific cryptographic functionalities. It is often used in applications that require secure data handling and encryption tailored to different regional settings. However, this package has been compromised, leading to severe security risks for any application utilizing it.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the crypto-locale package. This code can fully compromise any computer that has the package installed or running, allowing unauthorized access to sensitive information such as secrets and keys. The implications of this vulnerability are significant, as it can lead to data breaches and loss of control over the affected systems.

How To Fix

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

npm uninstall crypto-locale

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. Ensure that you monitor your system for any signs of compromise after removal.

Conclusion

The crypto-locale 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. Users are encouraged to utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for crypto-locale →

Share this vulnerability

FAQ

You should uninstall the crypto-locale package immediately and rotate any sensitive information stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

No, there is currently no patched version of the crypto-locale package. The only solution is to remove it completely.

Failing to remove the package can lead to unauthorized access to sensitive data and potential data breaches, compromising the security of your application.

It is highly discouraged to use crypto-locale due to the malicious code embedded within it. The best practice is to find an alternative package that provides similar functionality without the associated risks.

How To Fix

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

npm uninstall crypto-locale

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