Which versions of react-dynamic-table-compenent are malicious?

The following npm versions of react-dynamic-table-compenent are flagged malicious: 1.2.7. Treat any of these as compromised.

How do I remediate react-dynamic-table-compenent if I installed it?

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

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

If react-dynamic-table-compenent 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-dynamic-table-compenent part of a known attack campaign?

Yes — react-dynamic-table-compenent is associated with the IN-MAL-2026-007651 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-dynamic-table-compenent 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-dynamic-table-compenent (version 1.2.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-dynamic-table-compenent across your stack and pipelines.

Malicious package

react-dynamic-table-compenentnpm

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

MAL-2026-6533

Immediate action

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

npm uninstall react-dynamic-table-compenent

What this malware does

Package name misspells 'component' as 'compenent', a one-letter typosquat of react-dynamic-table-component. The package's postinstall script runs node dist/setup.js, which fetches https://everydaynodechecker-39143n.vercel.app/api/key?mem=master and passes the response body directly to eval(), inside a function misleadingly named initDatabase. The fetched content is attacker-controlled and mutable, so any default npm install of this package executes whatever code the endpoint currently serves on the installer's machine. The cover-story naming (initDatabase, key?mem=master) presents the request as benign configuration while it is a remote code loader.

Malicious versions

1 flagged

1.2.7

Indicators of compromise (SHA-256)

c55ead8b66faca1e08b2babafa252da2371b535c010a5c14d8b0d0e2a44aadf8

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-dynamic-table-compenent (version 1.2.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-dynamic-table-compenent across your stack and pipelines.
If you installed it — respond
react-dynamic-table-compenent is a typosquat — you almost certainly intended a legitimately-named package. Remove react-dynamic-table-compenent, 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-dynamic-table-compenent 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-dynamic-table-compenent 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-dynamic-table-compenent on npm has been identified as a malicious package (version 1.2.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007651

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks react-dynamic-table-compenent-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