Malicious Code Detected in h-jsencrypt Package - Security Alert

h-jsencrypt Updated 23 Jan 2026

Summary

23/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-495: Malicious code in h-jsencrypt (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 h-jsencrypt package is a JavaScript library used for encrypting and decrypting data using RSA. It is commonly utilized in web applications to secure sensitive information. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that rely on it.

Vulnerability Detail

The vulnerability originates from the h-jsencrypt package, which has been identified to contain malicious code that could compromise the integrity and security of applications using it. This malicious code may allow unauthorized access to sensitive data, leading to potential data breaches and exploitation of user information. The vulnerability affects all versions of the package starting from its introduction, making it critical for users to take immediate action.

How To Fix

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

npm uninstall h-jsencrypt

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 workaround, consider removing the h-jsencrypt package from your project until a secure version is available. You can do this by executing the following command: npm uninstall h-jsencrypt. Alternatively, you may explore other encryption libraries that do not have known vulnerabilities.

Conclusion

The h-jsencrypt package has been found to contain malicious code, posing serious security risks to applications utilizing it. Immediate action is required to update or remove the package to safeguard sensitive information. Utilize tools like Vulert to monitor your application for vulnerabilities effectively.

See every vulnerability recorded for h-jsencrypt →

Share this vulnerability

FAQ

The h-jsencrypt package is used for encrypting and decrypting data using RSA in JavaScript applications.

You can check if your application is affected by using Vulert, which monitors open-source vulnerabilities in your software. Visit Vulert Scanner to analyze your package-lock.json without any signup.

Using the compromised h-jsencrypt package can lead to unauthorized access to sensitive data, data breaches, and exploitation of user information.

Currently, there is no specific patched version available. It is recommended to update the package as soon as a secure version is released.

If immediate updates are not possible, consider removing the package or using alternative encryption libraries until a secure version is available.

How To Fix

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

npm uninstall h-jsencrypt

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