Which versions of gdwkh6vcbu are malicious?

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

How do I remediate gdwkh6vcbu if I installed it?

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

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

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

Yes — gdwkh6vcbu is associated with the GHSA-9hmh-j4x7-6958, IN-MAL-2026-017542 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 gdwkh6vcbu 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 gdwkh6vcbu (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gdwkh6vcbu across your stack and pipelines.

Malicious package

gdwkh6vcbunpm

gdwkh6vcbu is a confirmed malicious npm package (MAL-2026-13810) 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 gdwkh6vcbu (npm)

MAL-2026-13810

Immediate action

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

npm uninstall gdwkh6vcbu

What this malware does

Package [email protected] ships a single index.html declared as main, with no JavaScript entry point, no install lifecycle hooks, and placeholder-only metadata (random 10-character name, no description/author/repository/license, files list containing only index.html). The HTML impersonates a Cloudflare Turnstile 'Just a moment...' verification page. On Turnstile completion, obfuscator.io-style code (string-array + _0x2637 base64 decoder) constructs a URL whose host ends in 'loud.homes/', propagates the current page's query parameters to that URL, and calls window.location.assign to redirect the visitor. The package is not usable as a Node module; its sole purpose is to be served over npm-backed CDN mirrors (unpkg/jsdelivr) as a phishing landing/redirector page. npm install does not execute code on the installing developer, but the artifact abuses the npm namespace/CDN to host and distribute obfuscated phishing content targeting end-user browsers.

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)

114764d97df90695a2aff82ea409b230b1a283889fb5921a13cc054febe9fb68

149331c58c86a1da87dcdde4ec9e7f780a879ca2283946418cfff31077797bd4

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 gdwkh6vcbu (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gdwkh6vcbu across your stack and pipelines.
If you installed it — respond
gdwkh6vcbu is a typosquat — you almost certainly intended a legitimately-named package. Remove gdwkh6vcbu, 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 gdwkh6vcbu 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 gdwkh6vcbu 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. gdwkh6vcbu 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-9hmh-j4x7-6958IN-MAL-2026-017542

References

Credits

Amazon Inspector · finder

Detect & block this

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