# MAL-2026-10987: Malicious code in react-tabulix-core (npm)


- **Type:** Malicious package
- **Package:** `react-tabulix-core` (npm)
- **Published:** 21 Jul 2026
- **Also known as:** GHSA-5w4q-8fc9-88f4

## What is MAL-2026-10987?

MAL-2026-10987 is a malicious package in react-tabulix-core, published on 21 Jul 2026. 

### Official description

react-tabulix-core@0.1.0 declares a preinstall lifecycle hook that runs dist/index.d.js. That file base64-decodes an embedded blob and passes the resulting string to eval, invoked indirectly via globalThis[tag] where tag is assembled from the char-code sequence [101,118,97,108] ('eval') to evade static string search. The decoded payload performs an outbound HTTPS fetch to https://everydaynodechecker-39145n.vercel.app/api/key?mem=root3 and eval()s the response body. Result: on `npm install`, arbitrary attacker-controlled JavaScript from a third-party Vercel host executes on the installer's machine with the user's privileges. The obfuscation (base64 blob + char-code eval identifier) and the mutable remote payload source have no legitimate purpose in a UI component library.

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.

The OpenSSF Package Analysis project identified 'react-tabulix-core' @ 0.1.3 (npm) as malicious.

It is considered malicious because:

- The package executes one or more commands associated with malicious behavior.

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

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

## Sources

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

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