Critical Malicious Code Vulnerability in changelog-logger-utils Package

changelog-logger-utils Updated 19 Mar 2026

Summary

19/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1927: Malicious code in changelog-logger-utils (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 changelog-logger-utils package is an npm utility designed to assist developers in managing and logging changes in their projects. It is commonly used in various JavaScript applications to maintain a clear record of updates and modifications. However, this package has been found to contain malicious code that compromises the security of systems where it is installed.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the changelog-logger-utils package. This code can fully compromise any computer running the package, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code poses significant risks, as it may lead to data breaches and unauthorized control over the affected systems. Users are advised to treat any system with this package installed as compromised and take immediate action.

How To Fix

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

npm uninstall changelog-logger-utils

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

Currently, there are no effective workarounds to mitigate the risks associated with this vulnerability. The only recommended action is to uninstall the package and secure your system.

Conclusion

The changelog-logger-utils package has been identified as containing malicious code that poses serious security risks. Immediate uninstallation and rotation of sensitive information are critical steps to protect your systems. Regular monitoring of your dependencies using tools like Vulert can help prevent future vulnerabilities.

See every vulnerability recorded for changelog-logger-utils →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any secrets or keys stored on the affected system.

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

Keeping this package installed can lead to unauthorized access to sensitive information and complete control of your system by malicious actors.

After uninstalling the package, ensure to rotate all secrets and keys stored on the compromised system to prevent unauthorized access.

While you can use similar packages, ensure to review their security history and monitor them for vulnerabilities using tools like Vulert.

How To Fix

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

npm uninstall changelog-logger-utils

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