Malicious Code Detected in create-release-hash Package - Vulnerability Overview

create-release-hash Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17664: Malicious code in create-release-hash (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The create-release-hash package is an npm library designed to facilitate the generation of hash values for release management. It is commonly used in software development workflows to ensure the integrity of releases. However, this package has been identified to contain malicious code, posing significant risks to users who rely on it for secure release processes.

Vulnerability Detail

The vulnerability in the create-release-hash package stems from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code may lead to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall create-release-hash

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 temporary measure, users can avoid using the create-release-hash package and seek alternative libraries that provide similar functionality without the associated risks. Additionally, consider implementing security measures such as code reviews and dependency scanning to mitigate potential threats.

Conclusion

The discovery of malicious code in the create-release-hash package poses a significant threat to users. It is crucial to remove this package from your projects and seek alternatives to safeguard your applications. Regularly monitoring dependencies and utilizing tools like Vulert can help maintain security in your software development process.

See every vulnerability recorded for create-release-hash →

Share this vulnerability

FAQ

The create-release-hash package is used to generate hash values for software releases, ensuring the integrity and authenticity of the release process.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground without any signup.

If you have used the create-release-hash package, it is recommended to remove it from your project immediately and look for alternative solutions.

As of now, there is no patched version available for the create-release-hash package. Users should monitor the package repository for any updates.

Using the create-release-hash package can expose your application to security vulnerabilities, including unauthorized access and data breaches due to the malicious code embedded in the package.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall create-release-hash

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