Summary
Malicious Package in json-serializer
Version 2.0.10 of json-serializer contained malicious code. The code when executed in the browser would enumerate password, cvc, cardnumber fields from forms and send the extracted values to https://js-metrics.com/minjs.php?pl=
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Remove the package from your environment and evaluate your application to determine whether or not user data was compromised.
Frequently Asked Questions
- What is GHSA-CHH2-RVHG-WQWR? GHSA-CHH2-RVHG-WQWR is a critical-severity security vulnerability in json-serializer (npm), affecting versions = 2.0.10. It is fixed in 2.0.11.
- Which versions of json-serializer are affected by GHSA-CHH2-RVHG-WQWR? json-serializer (npm) versions = 2.0.10 is affected.
- Is there a fix for GHSA-CHH2-RVHG-WQWR? Yes. GHSA-CHH2-RVHG-WQWR is fixed in 2.0.11. Upgrade to this version or later.
- Is GHSA-CHH2-RVHG-WQWR exploitable, and should I be worried? Whether GHSA-CHH2-RVHG-WQWR is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-CHH2-RVHG-WQWR is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-CHH2-RVHG-WQWR? Upgrade
json-serializerto 2.0.11 or later.