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

GHSA-8gr3-2gjw-jj7g node-ipc

GHSA-8gr3-2gjw-jj7g is a security vulnerability in node-ipc. No vendor fix is recorded yet; mitigation options are listed below.

Hidden functionality in node-ipc

Published
Mar 16, 2022
Updated
Mar 16, 2022
Affected
1 pkg
Patched
None yet
Exploits
None indexed
Exploitation data as of Mar 16, 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.

427other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
node-ipcnpm
703Kdownloads / week

Description

The package node-ipc version 9.2.2 is vulnerable to hidden functionality that was introduced by the maintainer. The package uses a dependency that writes a file to disk that does not pertain to the functionality of the package and is not included in versions < 9.2.2.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmnode-ipcall 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 node-ipc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    No patched version of node-ipc has shipped for GHSA-8gr3-2gjw-jj7g 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-8gr3-2gjw-jj7g can be triaged on real exposure rather than presence alone.

Tailored to GHSA-8gr3-2gjw-jj7g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The package node-ipc version 9.2.2 is vulnerable to hidden functionality that was introduced by the maintainer. The package uses a dependency that writes a file to disk that does not pertain to the functionality of the package and is not included in versions < 9.2.2.
O3 Security · Impact-Aware SCA

Is GHSA-8gr3-2gjw-jj7g in your dependencies?

O3 Security finds GHSA-8gr3-2gjw-jj7g across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-8gr3-2gjw-jj7g: node-ipc | O3 Security