Critical Malicious Code Vulnerability in config-log Package

config-log Updated 02 Oct 2025

Summary

20/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6011: Malicious code in config-log (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 config-log package is an npm library used for managing configuration logs in Node.js applications. It is designed to facilitate logging and tracking of configuration changes, making it easier for developers to maintain and debug their applications. However, this package has been identified as containing malicious code, which poses a significant threat to any system that has it installed.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the config-log package. This code can compromise the security of any computer running the package, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code means that it can lead to severe security breaches, including data theft and system control by external entities. The vulnerability is classified under CWE-506, indicating that the product contains code that appears to be malicious in nature.

How To Fix

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

npm uninstall config-log

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 workaround, you can temporarily disable the use of the config-log package in your application until it is confirmed safe or a patched version is released. This can be done by commenting out any require statements or import statements related to config-log in your code.

Conclusion

The config-log package has been identified as containing malicious code that poses a significant security risk. It is essential to remove the package and take necessary precautions to secure your system. Regular monitoring for vulnerabilities using tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for config-log →

Share this vulnerability

FAQ

The config-log package is an npm library used for managing configuration logs in Node.js applications.

The malicious code can compromise your system, allowing unauthorized access to sensitive information and potentially giving control to external entities.

You should remove the config-log package immediately and rotate any secrets or keys stored on the affected computer.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json.

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

How To Fix

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

npm uninstall config-log

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