Malicious Code Detected in config-management-cli Package

config-management-cli Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17476: Malicious code in config-management-cli (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 config-management-cli package is an npm library designed for managing configuration settings in various applications. It provides functionalities that allow developers to easily handle configuration files and settings across different environments. However, this package has been identified to contain malicious code, posing a significant risk to users who rely on it for their projects.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the config-management-cli package. This code can potentially compromise the security of applications that utilize 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 config-management-cli

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, users can remove the config-management-cli package from their project until a secure version is released. This can be done using the command: npm uninstall config-management-cli. Alternatively, consider using a different package that offers similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the config-management-cli package highlights the importance of regularly monitoring and updating dependencies in software projects. Users are urged to take immediate action to mitigate potential risks by updating or removing the affected package.

See every vulnerability recorded for config-management-cli →

Share this vulnerability

FAQ

config-management-cli is an npm library used for managing configuration settings in applications.

The specific nature of the malicious code has not been disclosed, but it poses significant security risks to applications using the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Users are advised to check the package repository for any updates or patches that address this vulnerability.

As a temporary measure, consider uninstalling the package or using an alternative package until a secure version is available.

How To Fix

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

npm uninstall config-management-cli

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