Which versions of xhjckswqivb are malicious?

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

How do I remediate xhjckswqivb if I installed it?

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

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

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

Yes — xhjckswqivb is associated with the GHSA-6w4f-884x-xjcf, IN-MAL-2026-017506 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 xhjckswqivb across my projects, lockfiles, and CI pipelines?

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

Malicious package

xhjckswqivbnpm

Advisory published Aug 12, 2026Updated Aug 12, 2026

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

MAL-2026-13844

Immediate action

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

npm uninstall xhjckswqivb

What this malware does

Package contains only index.html and package.json. The HTML mimics a Cloudflare Turnstile challenge and, when loaded in a browser, assembles an obfuscated URL from the string fragments 'gin.microl' and 'ive.club/' and redirects the visitor to https://login.microlive.club/ with the original query string appended. package.json declares no preinstall/install/postinstall/prepare lifecycle scripts, and main points at the HTML file, so npm install and require do not execute any of this code on the installer. The victim of the artifact is an end-user who visits the served HTML, not a developer who installs the 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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

96d5b9889be154d9bae5b160e6b9cf2fb5a5a69c4b45c40ba2ff9bf8e386307c

9a9d37b433e22c980e67c0a2991612592959f6998df3928a6a09792ecf4860bb

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for xhjckswqivb (version 1.0.0).
If you installed it — respond
xhjckswqivb is a typosquat — you almost certainly intended a legitimately-named package. Remove xhjckswqivb, 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 xhjckswqivb 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. xhjckswqivb 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-6w4f-884x-xjcfIN-MAL-2026-017506

References

Credits

Amazon Inspector · finder

Detect & block this

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