# MAL-2026-13805: Malicious code in egair0810 (npm)


- **Type:** Malicious package
- **Package:** `egair0810` (npm)
- **Published:** 12 Aug 2026
- **Also known as:** GHSA-5vqp-mfpc-2j65

## What is MAL-2026-13805?

MAL-2026-13805 is a malicious package in egair0810, published on 12 Aug 2026. 

### Official description

The package contains a single index.html file declared as the package `main`, presenting a fake 'Just a moment...' / Cloudflare Turnstile page with heavily obfuscated JavaScript (string-array + shuffling style) that constructs a target URL from encoded strings and calls window.location.replace to redirect the browser. package.json declares no preinstall, install, postinstall, or prepare lifecycle scripts, and `main` points at an HTML file that Node cannot load as a module, so `npm install` and `require()` of the package do not execute the obfuscated code. The payload only runs if the HTML is opened in a browser. The artifact is not a functioning npm library and appears to be registry abuse hosting a browser-facing redirect/phishing lure rather than a supply-chain attack against 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-13805?

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

## Sources

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

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