Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm
Not in CISA KEV

GHSA-5w9c-rv96-fr7g faker

Fix: Marak/colors.js@074a0f8

GHSA-5w9c-rv96-fr7g is a security vulnerability in faker. No vendor fix is recorded yet; mitigation options are listed below.

Removal of functional code in faker.js

Published
Mar 22, 2022
Updated
Mar 22, 2022
Affected
1 pkg
Patched
See advisory
Exploits
None indexed
Exploitation data as of Mar 22, 2022 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

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.

2Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
fakernpm
1.6Mdownloads / week

Description

Faker.js helps users create large amounts of data for testing and development. The maintainer deliberately removed the functional code from this package. This appears to be a purposeful and successful attempt to make the package unusable. This is related to the colors.js CVE-2021-23567.

The functional code for this package was forked and can be found here.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmfakerall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for faker, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    No patched version of faker has shipped for GHSA-5w9c-rv96-fr7g yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-5w9c-rv96-fr7g can be triaged on real exposure rather than presence alone.

Tailored to GHSA-5w9c-rv96-fr7g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Faker.js helps users create large amounts of data for testing and development. The maintainer deliberately removed the functional code from this package. This appears to be a purposeful and successful attempt to make the package unusable. This is related to the colors.js [CVE-2021-23567](https://github.com/advisories/GHSA-gh88-3pxp-6fm8). The functional code for this package was forked and can be found [here](https://github.com/faker-js/faker).
O3 Security · Impact-Aware SCA

Is GHSA-5w9c-rv96-fr7g in your dependencies?

O3 Security finds GHSA-5w9c-rv96-fr7g across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-5w9c-rv96-fr7g: faker | O3 Security