Which versions of tuxcmdfhjkw are malicious?

The following npm versions of tuxcmdfhjkw are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate tuxcmdfhjkw if I installed it?

tuxcmdfhjkw is a typosquat — you almost certainly intended a legitimately-named package. Remove tuxcmdfhjkw, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

If tuxcmdfhjkw 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 tuxcmdfhjkw part of a known attack campaign?

Yes — tuxcmdfhjkw is associated with the GHSA-67q5-w9wg-mvvv, IN-MAL-2026-020438 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 tuxcmdfhjkw across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tuxcmdfhjkw (version 1.0.0).

Malicious package

tuxcmdfhjkwnpm

Advisory published Sep 23, 2026Updated Sep 23, 2026

tuxcmdfhjkw is a confirmed malicious npm package (MAL-2026-16458) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tuxcmdfhjkw (npm)

MAL-2026-16458

Immediate action

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

npm uninstall tuxcmdfhjkw

What this malware does

The package's only shipped file is an HTML page that mimics a Cloudflare 'Just a moment...' verification screen and embeds obfuscator.io-style JavaScript (_0xNNNN identifiers, string-array lookups) that runtime-constructs a URL beginning with 'https://ap' from decoded string-array entries. The package.json declares no preinstall/install/postinstall lifecycle scripts, and main points at an HTML file that Node cannot require, so installing or requiring the package does not execute the embedded script on the installer's machine. The content is a phishing page targeting browser users who might be steered to render it, i.e. registry abuse using npm as a content host rather than an attack on package installers.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

ee9b178308f2fb0e66b25444c0b033ae9057d8bf3b1d186c54e748edb4f5bf6f

ed907ab556a271a706db9227bfa0cd751f7a3dae9005bca41167ffdfc8be75b8

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for tuxcmdfhjkw (version 1.0.0).
If you installed it — respond
tuxcmdfhjkw is a typosquat — you almost certainly intended a legitimately-named package. Remove tuxcmdfhjkw, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If tuxcmdfhjkw 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. tuxcmdfhjkw on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-67q5-w9wg-mvvvIN-MAL-2026-020438

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tuxcmdfhjkw-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