Which versions of hxckdoeaqjlc8 are malicious?

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

How do I remediate hxckdoeaqjlc8 if I installed it?

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

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

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

Yes — hxckdoeaqjlc8 is associated with the GHSA-6gwr-m2g4-3mfv, IN-MAL-2026-017520 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 hxckdoeaqjlc8 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 hxckdoeaqjlc8 (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 hxckdoeaqjlc8 across your stack and pipelines.

Malicious package

hxckdoeaqjlc8npm

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

MAL-2026-13816

Immediate action

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

npm uninstall hxckdoeaqjlc8

What this malware does

The package ships a single HTML file that impersonates Cloudflare's 'Just a moment...' interstitial. On Turnstile widget callback, embedded JavaScript reconstructs the URL 'https://checkout.microlive.club/' from concatenated string fragments and calls window.location.replace to redirect the visitor to that host, forwarding any inbound query-string parameters via URLSearchParams. package.json declares no lifecycle scripts and 'main' points at the HTML file, so nothing executes on npm install or require. The artifact is a phishing/redirect landing page abusing the npm registry as static hosting; the target audience is browser visitors served this file elsewhere, not developers who install 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)

ee367d414649ecf8cd024630a6b1cd79c3623be3fc9cedca3581f2e453215a71

d324cd3fd06a0d97ae5fb9263df818bc505d28ebcdda8e90814b5630de70e108

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 hxckdoeaqjlc8 (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 hxckdoeaqjlc8 across your stack and pipelines.
If you installed it — respond
hxckdoeaqjlc8 is a typosquat — you almost certainly intended a legitimately-named package. Remove hxckdoeaqjlc8, 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 hxckdoeaqjlc8 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 hxckdoeaqjlc8 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. hxckdoeaqjlc8 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-6gwr-m2g4-3mfvIN-MAL-2026-017520

References

Credits

Amazon Inspector · finder

Detect & block this

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