Critical Malicious Code Vulnerability in jh5o Package

jh5o Updated 07 Jan 2026

Summary

07/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-116: Malicious code in jh5o (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The jh5o package is an npm module designed for specific functionalities within JavaScript applications. However, it has been identified as containing malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk as it can lead to unauthorized access and control over the affected systems.

Vulnerability Detail

The vulnerability originates from the jh5o package, which has been flagged for containing embedded malicious code. This code can fully compromise any computer that has the package installed, allowing attackers to gain control and access sensitive information, such as secrets and keys. The ramifications of this vulnerability are severe, as it not only affects the integrity of the system but also poses a risk to any data processed by the compromised machine.

How To Fix

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

npm uninstall jh5o

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 for this vulnerability other than removing the jh5o package and securing your system. Ensure that you monitor your system for any signs of compromise following the removal.

Conclusion

The jh5o package poses a critical security risk due to embedded malicious code. Immediate removal of the package and rotation of sensitive information is essential to protect your systems. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for jh5o →

Share this vulnerability

FAQ

jh5o is an npm package used in JavaScript applications, but it has been identified as containing malicious code.

If you have the jh5o package installed, your system is considered compromised. You should take immediate action to remove it.

After removal, rotate all secrets and keys stored on the affected system from a secure machine to prevent unauthorized access.

No, there is currently no patched version of the jh5o package available. The only solution is to uninstall it.

Vulert monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file, ensuring your applications remain secure.

How To Fix

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

npm uninstall jh5o

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