Malicious Code Detected in constant_resolver Package - Immediate Action Required

constant_resolver Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17499: Malicious code in constant_resolver (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The constant_resolver package is an npm library designed to facilitate the resolution of constants in JavaScript applications. It is commonly used for managing configuration values and constants across various modules. However, recent findings have revealed that this package contains malicious code, posing significant risks to applications that rely on it.

Vulnerability Detail

The vulnerability in the constant_resolver package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall constant_resolver

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 temporary workaround, consider removing the constant_resolver package from your project until a secure version is available. You can do this by executing: npm uninstall constant_resolver. This will help mitigate the risks associated with the malicious code while you seek alternative solutions.

Conclusion

The discovery of malicious code in the constant_resolver package poses a serious threat to applications that utilize it. Immediate action is required to update or remove the package to safeguard your projects. Regular monitoring and using tools like Vulert can help in identifying such vulnerabilities in the future.

See every vulnerability recorded for constant_resolver →

Share this vulnerability

FAQ

The constant_resolver package is an npm library used for managing constants in JavaScript applications.

The malicious code found in the constant_resolver package can lead to unauthorized access and potential data breaches.

You can check if your application is affected by using Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground without signup.

If you cannot update the package right away, consider removing it from your project as a temporary measure to reduce risk.

Currently, there is no specific patched version mentioned, but users should regularly check the package repository for updates.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall constant_resolver

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