# MAL-2026-13814: Malicious code in hlksdcixycvf (npm)


- **Type:** Malicious package
- **Package:** `hlksdcixycvf` (npm)
- **Published:** 12 Aug 2026
- **Also known as:** GHSA-q294-wj6j-h556

## What is MAL-2026-13814?

MAL-2026-13814 is a malicious package in hlksdcixycvf, published on 12 Aug 2026. 

### Official description

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.

## What should I do about MAL-2026-13814?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-13814 is a malicious package: hlksdcixycvf (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-13814/ (Markdown: https://insights.sbomify.com/MAL-2026-13814/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-13814

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-13814/
Summaries are generated and may contain mistakes; the official description above is the record.