Critical Malicious Code Vulnerability in changelog-logger-wrap Package

changelog-logger-wrap Updated 19 Mar 2026

Summary

19/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1928: Malicious code in changelog-logger-wrap (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-wrap package is an npm library designed to assist developers in managing and logging changes in their projects. It is commonly used in JavaScript applications to maintain a clear history of modifications and updates. However, this package has been compromised, leading to severe security risks for any application that utilizes it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the changelog-logger-wrap package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code has been confirmed by security researchers, and it poses a significant threat to the integrity and confidentiality of affected systems.

How To Fix

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

npm uninstall changelog-logger-wrap

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 the changelog-logger-wrap package. The only recommended action is to uninstall the package entirely.

Conclusion

The changelog-logger-wrap package has been identified as containing malicious code that poses a significant security risk. Immediate action is required to uninstall the package and secure any sensitive information. Regular monitoring of your dependencies using tools like Vulert can help prevent future vulnerabilities.

See every vulnerability recorded for changelog-logger-wrap →

Share this vulnerability

FAQ

It is an npm library used for managing and logging changes in JavaScript projects.

The malicious code can compromise your system, allowing unauthorized access to sensitive information.

You should uninstall the changelog-logger-wrap package immediately and rotate any sensitive keys or secrets.

No, there is currently no patched version of the changelog-logger-wrap package available.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

How To Fix

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

npm uninstall changelog-logger-wrap

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