npm · Malicious package advisory
Malwarereact-dynammic-table-component
MAL-2026-6534
Malicious code in react-dynammic-table-component (npm)
Details
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (d47aff9bb18dcd61350fa86e19d97ddee5ee7c5bdf7f0adea4a685e89d58fa4f) react-dynammic-table-component@1.2.7 declares a `preinstall` lifecycle script (`node dist/setup.js`) that runs automatically on `npm install`. The script issues an HTTPS GET to https://everydaynodechecker-39143n.vercel.app/api/key?mem=master and passes the response body directly to `eval()`, executing attacker-controlled JavaScript on the installer's machine with the user's privileges. The fetch+eval primitive is wrapped in a function named `initDatabase` that performs no database work — a cover-story label inside an otherwise unrelated React table UI component. The destination host is not a publisher/CDN domain for this package and the fetched content is unpinned, unverified, and mutable by whoever controls the Vercel deployment, so the executed code can be changed at any time without republishing the package. Installer harm is immediate and unbounded: any code the operator of the endpoint chooses to serve runs at install time (credential theft, persistence, lateral movement, dependency tampering, etc.). ## Source: ghsa-malware (dafb05a40352ab1ea42be7af01a26ba6ecfb8b58bc4eb0163dbd27bb7b379a0f) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. ## Source: ossf-package-analysis (3bd536e15a72ad0dd7b3ceece502e73cd29c606ea4d22efa16da366740ebf22f) The OpenSSF Package Analysis project identified 'react-dynammic-table-component' @ 1.2.7 (npm) as malicious. It is considered malicious because: - The package executes one or more commands associated with malicious behavior.
Compromised versions (1)
- 1.2.7
Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.