Critical Malicious Code Vulnerability in testxhjhk Package

testxhjhk Updated 27 Jan 2026

Summary

27/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-544: Malicious code in testxhjhk (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The testxhjhk package is an npm library that is used for various 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 to developers and organizations relying on this package for their projects.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the testxhjhk package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code is classified under CWE-506, indicating that it contains embedded malicious code. The ramifications of this vulnerability are severe, as it can lead to data breaches and unauthorized control over affected systems.

How To Fix

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

npm uninstall testxhjhk

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, ensure that all secrets and keys stored on the compromised computer are rotated immediately from a different, secure computer. This action is crucial to mitigate the risk of unauthorized access.

Conclusion

The testxhjhk package contains a critical vulnerability due to embedded malicious code, posing significant risks to any system where it is installed. Immediate action is required to remove the package and secure sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for testxhjhk →

Share this vulnerability

FAQ

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

The malicious code can fully compromise your system, allowing unauthorized access to sensitive information and control over your computer.

You should remove the testxhjhk package immediately and rotate any secrets or keys stored on the affected computer.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. You can check your application using the Vulert playground without any signup.

Vulert is a monitoring tool that uses package-lock.json to track and alert in real-time for open-source vulnerabilities in your software.

How To Fix

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

npm uninstall testxhjhk

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