# MAL-2026-17939: Malicious code in ticketcathayoct12 (npm)


- **Type:** Malicious package
- **Package:** `ticketcathayoct12` (npm)
- **Published:** 19 Oct 2026
- **Also known as:** GHSA-g7mg-3h9r-c8h3

## What is MAL-2026-17939?

MAL-2026-17939 is a malicious package in ticketcathayoct12, published on 19 Oct 2026. 

### Official description

The package ships a single file, index.html, which impersonates a Cloudflare 'Just a moment...' interstitial and embeds a Turnstile widget plus an obfuscator.io-obfuscated script containing hardcoded hostKey, aesKeyBase64, turnstileSiteKey, and a challengeLayoutHtml. The obfuscated code wires an onTurnstileComplete handler to window.__challengeRedirect, driving a client-side redirect after the Turnstile challenge completes. The package name (ticketcathayoct12) and content are consistent with a Cathay Pacific-themed phishing campaign, and the package appears to serve as a hosting vehicle so the HTML can be fetched through an npm-backed CDN. There are no lifecycle scripts and package.json main points at the HTML file, so npm install and require() of this package do not execute the content on an installer's machine; the harm target is end-user browsers that load the file via a CDN URL, 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.

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

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-17939 is a malicious package: ticketcathayoct12 (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-17939/ (Markdown: https://insights.sbomify.com/MAL-2026-17939/index.md)
```

## Sources

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

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