Critical Malicious Code Vulnerability in @emilgroup/changelog-sdk-node Package

Summary

22/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-2040: Malicious code in @emilgroup/changelog-sdk-node (npm). Affects @emilgroup/changelog-sdk-node versions 1.0.3. 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 @emilgroup/changelog-sdk-node package is an npm library designed to assist developers in managing and generating changelogs for their projects. It provides functionalities to automate the changelog creation process, making it easier to track changes and updates in software development. However, this package has been identified to contain malicious code, posing a significant security risk to any system utilizing it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the @emilgroup/changelog-sdk-node package. Any system with this package installed is considered fully compromised, as it may allow unauthorized access to sensitive information, including secrets and keys stored on the affected computer. The malicious code can lead to severe ramifications, including data breaches and loss of control over the system. Users are advised to treat any system running this package 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 @emilgroup/changelog-sdk-node

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

There are no effective workarounds to mitigate the risks associated with this vulnerability. The best course of action is to remove the package entirely and secure your system.

Conclusion

The @emilgroup/changelog-sdk-node package has been identified as containing malicious code, posing a severe security risk to any system that has it installed. Immediate action is required to uninstall the package and secure any sensitive information. Regular monitoring of dependencies is essential to prevent future vulnerabilities.

See every vulnerability recorded for @emilgroup/changelog-sdk-node →

Share this vulnerability

FAQ

Immediately uninstall the package using npm uninstall @emilgroup/changelog-sdk-node and rotate any sensitive information stored on the affected system.

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

Leaving the package installed can lead to unauthorized access to sensitive data, potential data breaches, and loss of control over your system.

Currently, there is no patched version available for this package. The only solution is to uninstall it.

Regularly monitor your dependencies using tools like Vulert, keep your packages updated, and review the security advisories for any libraries you use.

How To Fix

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

npm uninstall @emilgroup/changelog-sdk-node

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