# MAL-2026-10444: Malicious code in markable-table (npm)


- **Type:** Malicious package
- **Package:** `markable-table` (npm)
- **Published:** 13 Jul 2026
- **Also known as:** GHSA-qc34-pqm6-35rf

## What is MAL-2026-10444?

MAL-2026-10444 is a malicious package in markable-table, published on 13 Jul 2026. 

### Official description

markable-table@3.1.8 declares scripts.preinstall = 'node index.d.js'. index.d.js base64-decodes an embedded payload and invokes it through an identifier reconstructed from a char-code array ([101,118,97,108] = 'eval'), hiding the 'eval' token from plain-text scanners. The decoded payload fetches JavaScript from https://everydaynodechecker-39143n.vercel.app/api/key?mem=root0 and eval()s the response body at npm install time, giving the operator of that endpoint arbitrary code execution on any machine that runs `npm install`. The remote-fetch-and-eval, the obfuscation of both the 'eval' identifier and the destination URL, the non-first-party Vercel host, and the mismatch with the package's advertised markdown-table purpose (and typosquat of the popular 'markdown-table' package) together match the install-time-RCE dropper pattern.

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

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

## Sources

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

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