Critical Malicious Code Vulnerability in sha256-pack (npm)

sha256-pack Updated 02 Oct 2025

Summary

22/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6198: Malicious code in sha256-pack (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The sha256-pack package is an npm library designed for computing SHA-256 hashes efficiently. It is commonly used in various applications that require secure hashing. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on, making it a significant threat to developers and users alike.

Vulnerability Detail

The vulnerability originates from the inclusion of embedded malicious code within the sha256-pack package. This code can lead to complete system compromise, allowing unauthorized access to sensitive information such as secrets and keys stored on the affected computer. The malicious nature of this code poses severe risks, as it can operate undetected, potentially leading to data breaches and unauthorized control over the system.

How To Fix

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

npm uninstall sha256-pack

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 workaround, it is recommended to rotate all secrets and keys stored on the affected computer from a different, secure machine. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The sha256-pack package has been identified as containing malicious code that poses a serious threat to system security. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring and preventing future vulnerabilities.

See every vulnerability recorded for sha256-pack →

Share this vulnerability

FAQ

You should remove the sha256-pack package immediately and rotate any sensitive information stored on the affected machine.

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

Keeping sha256-pack installed can lead to unauthorized access to your system, potential data breaches, and loss of control over sensitive information.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.

The malicious code can compromise the entire system, allowing attackers to access and manipulate sensitive data, leading to severe security breaches.

How To Fix

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

npm uninstall sha256-pack

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