Which versions of twcvhjlksdmx are malicious?

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

How do I remediate twcvhjlksdmx if I installed it?

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

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

If twcvhjlksdmx was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is twcvhjlksdmx part of a known attack campaign?

Yes — twcvhjlksdmx is associated with the GHSA-pw3v-jpfx-hh5w, IN-MAL-2026-017417, IN-MAL-2026-017440 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 twcvhjlksdmx across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for twcvhjlksdmx (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging twcvhjlksdmx across your stack and pipelines.

Malicious package

twcvhjlksdmxnpm

twcvhjlksdmx is a confirmed malicious npm package (MAL-2026-13836) that typosquats a legitimate package to trick installs (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in twcvhjlksdmx (npm)

MAL-2026-13836

Immediate action

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

npm uninstall twcvhjlksdmx

What this malware does

The tarball contains only package.json and index.html. package.json declares no preinstall/install/postinstall/prepare lifecycle hooks and sets main to index.html, which is not a loadable JavaScript module and will not execute on npm install or on require(). index.html impersonates a Cloudflare 'Just a moment' interstitial and embeds an obfuscator.io-style script (string-array + base64 _0x5844 decoder) that constructs a URL and calls window.location.replace to redirect the browser. The redirect only fires if a user opens the HTML file in a browser; it does not run against a developer or build system that installs or requires this package.

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

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

9b23aefc385a2c9eb5243177ecee09d4e2490a26764cf686946d343cbab9fe53

60b37bf3e91951e089b31d7aa6d31834fef110ba5bfc1c8c3cb09e701c9c1878

799b4b725cf0fc509be84ebef8ce52e119581d1ea493521523745e9208997beb

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for twcvhjlksdmx (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging twcvhjlksdmx across your stack and pipelines.
If you installed it — respond
twcvhjlksdmx is a typosquat — you almost certainly intended a legitimately-named package. Remove twcvhjlksdmx, 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 twcvhjlksdmx was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks twcvhjlksdmx before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. twcvhjlksdmx on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-pw3v-jpfx-hh5wIN-MAL-2026-017417IN-MAL-2026-017440

References

Credits

Amazon Inspector · finder

Detect & block this

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