# GHSA-8gr3-2gjw-jj7g: Hidden functionality in node-ipc

> Malicious hidden functionality in node-ipc writes unauthorized files to disk, requiring users to upgrade to a safe version.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Mar 2022

## What is GHSA-8gr3-2gjw-jj7g?

GHSA-8gr3-2gjw-jj7g is a vulnerability in node-ipc, published on 16 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

## Which versions are affected by GHSA-8gr3-2gjw-jj7g?

2 open source packages ship an affected version, including node-ipc.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node-ipc` | npm | All versions | None |
| `node-ipc` | npm | All versions | None |

## How do I fix GHSA-8gr3-2gjw-jj7g?

No fix has been published for GHSA-8gr3-2gjw-jj7g yet. Limit exposure of the affected software until one is available.

## Is GHSA-8gr3-2gjw-jj7g being exploited?

There is no known exploitation of GHSA-8gr3-2gjw-jj7g in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-8gr3-2gjw-jj7g and fix it if it is affected.

What it is: GHSA-8gr3-2gjw-jj7g is a vulnerability in node-ipc, published on 16 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-8gr3-2gjw-jj7g in the wild and no public exploit code.

Affected packages and fixed versions:
- node-ipc (npm): affected all versions; no fix listed
- node-ipc (npm): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-8gr3-2gjw-jj7g/ (Markdown: https://insights.sbomify.com/GHSA-8gr3-2gjw-jj7g/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-8gr3-2gjw-jj7g

---
From sbomify Insights: https://insights.sbomify.com/GHSA-8gr3-2gjw-jj7g/
Summaries are generated and may contain mistakes; the official description above is the record.