Critical Malicious Code Vulnerability in luxon-js Package

luxon-js Updated 12 Jan 2026

Summary

12/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-228: Malicious code in luxon-js (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 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 luxon-js package is a popular JavaScript library used for date and time manipulation. It provides a comprehensive API for handling dates, times, and durations, making it a valuable tool for developers. However, recent findings have revealed that this package contains malicious code, posing significant security risks to any system that has it installed.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the luxon-js package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to a malicious actor who has injected harmful code into the package, which can lead to complete control of the affected system. Users are advised to treat any system running this package as fully compromised.

How To Fix

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

npm uninstall luxon-js

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 luxon-js package entirely from your system.

Conclusion

The luxon-js package has been identified as containing malicious code that compromises the security of any system it is installed on. Immediate removal of the package and rotation of sensitive information is essential to mitigate the risks associated with this vulnerability.

See every vulnerability recorded for luxon-js →

Share this vulnerability

FAQ

You should remove the luxon-js package from your system immediately and rotate any secrets or keys stored on that computer.

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

Currently, there is no patched version available. The best course of action is to remove the package entirely.

Failing to address this vulnerability can lead to unauthorized access to sensitive data and complete control of your system by malicious actors.

It is strongly advised to remove luxon-js regardless of the sensitivity of the information stored, as the malicious code can still pose significant risks.

How To Fix

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

npm uninstall luxon-js

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