Malicious Code Detected in auto_release_notes Package
Summary
MAL-2025-15108: Malicious code in auto_release_notes (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The auto_release_notes package is an npm tool designed to automate the generation of release notes for software projects. It aims to streamline the release process by aggregating changes and updates into a coherent format. However, this package has been found to contain malicious code, posing a significant risk to users who rely on it for their development workflows.
Vulnerability Detail
The vulnerability in the auto_release_notes package stems from the inclusion of malicious code that can compromise the integrity of the software using it. This code could potentially lead to unauthorized access, data breaches, or other harmful actions within the user's environment. The malicious nature of this code was identified in a recent security audit, highlighting the importance of scrutinizing third-party packages before integration.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall auto_release_notesIf 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 measure, users can avoid using the auto_release_notes package and manually create release notes based on their project's commit history. This can be done by reviewing the git logs and summarizing the changes without relying on automated tools.
Conclusion
The discovery of malicious code in the auto_release_notes package underscores the importance of vigilance when using third-party libraries. Users are advised to remove the package and monitor their projects for any unusual activity. Regularly checking for updates and utilizing vulnerability monitoring tools can help mitigate risks associated with open-source dependencies.
See every vulnerability recorded for auto_release_notes →
FAQ
The malicious code can potentially allow unauthorized access or manipulation of the user's environment, posing security risks.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
It is crucial to remove the package immediately and assess any potential impacts it may have had on your project.
While specific exploits have not been detailed, the presence of malicious code indicates a high risk of exploitation.
Utilizing tools like Vulert can help you monitor your dependencies for vulnerabilities in real-time.
