Malicious Package in react-datepicker-plusGHSA-4wcx-c9c4-89p2
CRITICALGHSA-4wcx-c9c4-89p2 is a critical-severity (CVSS 9.8) vulnerability in react-datepicker-plus. A fix is available for react-datepicker-plus — see the affected versions and patch details below.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
react-datepicker-plusnpmDescription
Versions 2.4.3 and 2.4.2 of react-datepicker-plus contained malicious code. The code when executed in the browser would enumerate password, cvc and cardnumber fields from forms and send the extracted values to https://js-metrics.com/minjs.php?pl=
Recommendation
Remove the package from your environment and evaluate your application to determine whether or not user data was compromised.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | react-datepicker-plus | ≥ 2.4.2&&< 2.4.6 | 2.4.6npm install react-datepicker-plus@2.4.6 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for react-datepicker-plus, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update react-datepicker-plus to 2.4.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4wcx-c9c4-89p2 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-4wcx-c9c4-89p2 in your dependencies?
Find it across npm, including transitive dependencies.