# MAL-2026-10452: Malicious code in markdown-editable-table (npm)


- **Type:** Malicious package
- **Package:** `markdown-editable-table` (npm)
- **Published:** 13 Jul 2026
- **Also known as:** GHSA-jf3r-qgv3-frvm

## What is MAL-2026-10452?

MAL-2026-10452 is a malicious package in markdown-editable-table, published on 13 Jul 2026. 

### Official description

The package's package.json declares a preinstall hook (`node index.d.js`) that runs automatically on `npm install`. The script in index.d.js base64-decodes a payload whose decoded body fetches JavaScript from https://everydaynodechecker-39143n.vercel.app/api/key?mem=root1 and passes the response to `eval`. Both the destination URL (hidden inside a base64 blob) and the `eval` identifier (reassembled from the char-code array [101,118,97,108] via String.fromCharCode and invoked as `globalThis[tag](text)`) are obfuscated. The package metadata (repository `wooorm/markdown-table`, description, funding) impersonates the legitimate `markdown-table` package while shipping unrelated code, indicating a typosquat lure. Installing the package results in arbitrary attacker-controlled JavaScript executing on the installer's machine.

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-10452?

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

## Sources

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

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