react-tabulix-corenpm
react-tabulix-core is a confirmed malicious npm package (MAL-2026-10987) that executes malicious code on install (malicious versions 0.1.0, 0.1.1, 0.1.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in react-tabulix-core (npm)
What this malware does
[email protected] 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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-tabulix-core (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-tabulix-core across your stack and pipelines.
If you installed it — respond
Remove react-tabulix-core from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If react-tabulix-core was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks react-tabulix-core before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks react-tabulix-core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.