Which versions of hlksdcixycvf are malicious?

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

How do I remediate hlksdcixycvf if I installed it?

Remove hlksdcixycvf from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

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

Yes — hlksdcixycvf is associated with the GHSA-q294-wj6j-h556, IN-MAL-2026-017504 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 hlksdcixycvf 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 hlksdcixycvf (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 hlksdcixycvf across your stack and pipelines.

Malicious package

hlksdcixycvfnpm

hlksdcixycvf is a confirmed malicious npm package (MAL-2026-13814) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hlksdcixycvf (npm)

MAL-2026-13814

Immediate action

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

npm uninstall hlksdcixycvf

What this malware does

The tarball contains a single file, index.html, declared as the package main. The HTML renders a Cloudflare Turnstile-themed 'verification' page containing obfuscator.io-style JavaScript that, on Turnstile callback, reconstructs a target URL and calls window.location.replace to redirect the browser. package.json declares no preinstall/install/postinstall/prepare lifecycle scripts, and npm cannot require an HTML main, so installing or importing this package performs no code execution on a developer machine. The obfuscated redirect only fires if a human opens index.html in a browser and completes the Turnstile widget; the target audience is browser visitors, not npm installers. The package appears to be abuse of the npm registry as static hosting for an obfuscated redirector / likely phishing landing page rather than a supply-chain attack against 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)

55ac0a25905ea75ffddc5737870427cd948ac76eb9ed6a3fae945cbb7b411ac5

e91dec68a77b15daa1f923bcfe876d283a8fea8d8cdf3d2ea27888b8eb522b97

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for hlksdcixycvf (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 hlksdcixycvf across your stack and pipelines.
If you installed it — respond
Remove hlksdcixycvf from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If hlksdcixycvf 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 hlksdcixycvf 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. hlksdcixycvf 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-q294-wj6j-h556IN-MAL-2026-017504

References

Credits

Amazon Inspector · finder

Detect & block this

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