Malicious Code Detected in consul-lock-sessions Package

consul-lock-sessions Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17502: Malicious code in consul-lock-sessions (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 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 consul-lock-sessions package is an npm library designed to manage session locks in applications that utilize Consul for service discovery and configuration. It is intended to provide developers with a reliable way to handle session states in distributed systems. However, this package has been found to contain malicious code, posing significant risks to applications that depend on it.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the consul-lock-sessions package. This code can potentially compromise the security of applications using the package, leading to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action.

How To Fix

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

npm uninstall consul-lock-sessions

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 measure, you can replace the functionality provided by consul-lock-sessions with an alternative package that offers similar features without the security risks. Ensure to review the alternatives thoroughly before implementation.

Conclusion

The discovery of malicious code in the consul-lock-sessions package highlights the importance of regularly auditing open-source dependencies. Users are advised to uninstall the affected package and monitor for updates or alternatives to ensure the security of their applications.

See every vulnerability recorded for consul-lock-sessions →

Share this vulnerability

FAQ

It is an npm library used for managing session locks in applications that utilize Consul for service discovery.

The malicious code was identified by security researchers from Amazon Inspector during routine checks of open-source packages.

Using the affected package can lead to unauthorized access, data breaches, and other security vulnerabilities in your application.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

Currently, there is no patched version available. It is recommended to uninstall the package until a secure version is released.

How To Fix

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

npm uninstall consul-lock-sessions

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