Malicious Package in json-serializer
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (json-serializer 2.0.11), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm json-serializer
- Affected
- >= 2.0.10, <= 2.0.10
- Fixed in
- 2.0.11
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-chh2-rvhg-wqwr lists affected ranges: npm json-serializer >=2.0.10 <2.0.11 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-chh2-rvhg-wqwr lists affected ranges: npm json-serializer >=2.0.10 <=2.0.10
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
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= Recommendation Remove the package from your environment and evaluate your application to determine whether or not user data was compromised.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-chh2-rvhg-wqwr
- Revision 1 · created ·
Published from osv record GHSA-chh2-rvhg-wqwr
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-chh2-rvhg-wqwr Advisory: Malicious Package in json-serializer IDs: GHSA-chh2-rvhg-wqwr Record: https://patchnext.com/advisories/ghsa-chh2-rvhg-wqwr (revision 2, source checked 26 Oct 2026, 12:15 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: json-serializer 2.0.11. A vendor fix does not mean a deployment is fixed. ## Affected components - npm json-serializer: affected >= 2.0.10, <= 2.0.10; fixed in 2.0.11 ## Suggested inspection (read-only) - `npm ls json-serializer --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on json-serializer. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-chh2-rvhg-wqwr (OSV record GHSA-chh2-rvhg-wqwr lists affected ranges: npm json-serializer >=2.0.10 <2.0.11 (fixed)) - Verified: https://github.com/advisories/GHSA-chh2-rvhg-wqwr (GitHub-reviewed advisory GHSA-chh2-rvhg-wqwr lists affected ranges: npm json-serializer >=2.0.10 <=2.0.10) Commands are suggestions: review each one before running it.
Loading voting…