Critical Malicious Code Vulnerability in tlxbnhd Package

tlxbnhd Updated 22 Sep 2026

Summary

22/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16385: Malicious code in tlxbnhd (npm). Affects tlxbnhd versions 0.0.1. 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 tlxbnhd package is an npm library that is used for various functionalities within JavaScript applications. However, it has been identified to contain malicious scripts that can compromise the integrity of systems where it is installed. This vulnerability arises from the inclusion of obfuscated lifecycle scripts that execute harmful actions during the installation process.

Vulnerability Detail

The vulnerability is rooted in the tlxbnhd package, which includes obfuscated preinstall.js and postinstall.js scripts. These scripts download executable files from a suspicious URL and run them on the user's system, potentially leading to unauthorized access or data breaches. The malicious code is hidden within a rotating string array, making it difficult to detect. This vulnerability can result in severe consequences, including system compromise and data loss.

How To Fix

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

npm uninstall tlxbnhd

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, you can prevent the installation of the tlxbnhd package by using npm's package-lock.json to lock your dependencies. Additionally, consider using the following command to uninstall the package: npm uninstall tlxbnhd.

Conclusion

The tlxbnhd package contains a critical vulnerability due to embedded malicious code that can compromise systems. It is essential to remove the package and monitor your applications for vulnerabilities using tools like Vulert. Always stay updated with the latest security patches to protect your software.

See every vulnerability recorded for tlxbnhd →

Share this vulnerability

FAQ

The tlxbnhd package is an npm library that provides various functionalities for JavaScript applications, but it has been compromised with malicious code.

The malicious code operates by downloading and executing harmful files during the installation process, which can lead to system compromise.

If you have installed tlxbnhd, you should immediately uninstall it and check for any updates or patches that may address the vulnerability.

Yes, you can use Vulert to monitor and alert you in real-time for open-source vulnerabilities in your software without needing access to the code.

You can check if your application is affected by using the Vulert playground at Vulert Scanner, which allows you to analyze your package-lock.json for vulnerabilities without signing up.

How To Fix

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

npm uninstall tlxbnhd

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