MalwarePublished 26 Jun 2026Updated 13 Jul 2026

react-dynamic-table-compenent (npm) · Malicious Code

Affects react-dynamic-table-compenentSource GCVE Database

Malicious package : remove react-dynamic-table-compenent and rotate any secrets on hosts that installed it.

Data as of 14 Jul 2026, 10:59 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-6533

What to do

Remove react-dynamic-table-compenent from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmreact-dynamic-table-compenent	Affected =1.2.7	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The npm package react-dynamic-table-compenent (version 1.2.7) is a malicious typosquat of react-dynamic-table-component. Its postinstall script executes attacker-controlled code fetched from a remote server using eval(), resulting in arbitrary code execution on the installer's machine. Installation of this package can lead to full system compromise, requiring immediate secret and key rotation and package removal.

Impact

Installation of this package leads to arbitrary code execution on the victim's machine, resulting in full system compromise. Attackers can execute any code with the privileges of the user installing the package, potentially stealing secrets, keys, and other sensitive data. The compromise is severe enough that all secrets and keys stored on the affected system should be rotated immediately from a different, trusted machine. Removal of the package alone does not guarantee full remediation due to potential persistence mechanisms installed by the attacker.

Defensive guidance

The recommended mitigation is to immediately remove the react-dynamic-table-compenent package version 1.2.7 from any affected systems. All secrets, keys, and credentials stored on compromised machines should be considered exposed and must be rotated from a secure, uncompromised environment. Due to the high risk of full system compromise, affected systems should be thoroughly inspected for additional malicious artifacts and potentially rebuilt if full trust cannot be restored.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Jul 2026, 10:59 UTC

Technical details

References

Community reviews