react-dynammic-table-componentnpm
Malicious code in react-dynammic-table-component (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
[email protected] 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.).
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-dynammic-table-component (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-dynammic-table-component across your stack and pipelines.
If you installed it — respond
react-dynammic-table-component is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If react-dynammic-table-component 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-dynammic-table-component 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 react-dynammic-table-component-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.