react-table-corenpm
react-table-core is a confirmed malicious npm package (MAL-2026-12425) that typosquats a legitimate package to trick installs (malicious version 2.7.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in react-table-core (npm)
What this malware does
package.json declares preinstall: node./dist/index.d.js, disguising an executable loader as a TypeScript declaration file. On npm install, that loader reads an AES-256-CBC ciphertext assembled at runtime by concatenating four fields (title/subtitle/description/tag) of a TASK_CONTENT object exported from./config.js, decrypts it with a hardcoded key and IV via crypto.createDecipheriv('aes-256-cbc', wad, ray), and passes the plaintext to eval — where eval is obtained by building the string from the char-code array [101,118,97,108] and looking it up on globalThis. This yields arbitrary attacker-controlled code execution on every machine that installs the package. The package is named react-table-core (typosquatting the popular react-table / @tanstack/react-table libraries) while the README is titled react-tabulix-query with unrelated Tabulix branding — the name/README mismatch is the lure for installations. Splitting the ciphertext across metadata-shaped fields, hiding the loader behind a .d.js extension, and reconstructing eval from char codes have no legitimate purpose in a React table utility.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-table-core (version 2.7.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-table-core across your stack and pipelines.
If you installed it — respond
react-table-core is a typosquat — you almost certainly intended a legitimately-named package. Remove react-table-core, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If react-table-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-table-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
Detect & block this
O3 blocks react-table-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.