Which versions of tlxbnhd are malicious?

The following npm versions of tlxbnhd are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate tlxbnhd if I installed it?

Remove tlxbnhd from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed tlxbnhd — how do I know if it already compromised me?

If tlxbnhd was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is tlxbnhd part of a known attack campaign?

Yes — tlxbnhd is associated with the IN-MAL-2026-020291 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find tlxbnhd across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tlxbnhd (version 0.0.1).

Malicious package

tlxbnhdnpm

Advisory published Sep 22, 2026Updated Sep 22, 2026

tlxbnhd is a confirmed malicious npm package (MAL-2026-16385) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tlxbnhd (npm)

MAL-2026-16385

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall tlxbnhd

What this malware does

The tlxbnhd package ships obfuscated preinstall.js and postinstall.js lifecycle scripts that, on npm install, download two files from https://api.imghippo.com/files/hOG8244hc.png (an anonymous image-hosting URL disguised with a.png extension), write them into the package directory as gldriver_pre_core.exe and gldriver_pre_asset.exe, and launch them using platform-specific commands (start on Windows, open on macOS, xdg-open/mspaint on Linux). After launch the scripts unlink the dropped files to remove traces. The URLs, filenames, and shell commands are hidden inside an obfuscator.io-style rotating string array with an index-shifting IIFE. The same dropper runs from both preinstall and postinstall, so it executes twice per install.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e415dbf226269704c2cd28b1783cf594f96880dd4688b26caf7f25a19e268237

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for tlxbnhd (version 0.0.1).
If you installed it — respond
Remove tlxbnhd from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If tlxbnhd was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. tlxbnhd on npm has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020291

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tlxbnhd-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database