# GHSA-3mpp-xfvh-qh37: node-ipc behavior change

> The node-ipc library writes a maintainer message to the user's desktop, requiring an upgrade to remove this unwanted behavior.

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

## What is GHSA-3mpp-xfvh-qh37?

GHSA-3mpp-xfvh-qh37 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

node-ipc starting in version 11.0.0 and prior to version 12.0.0 includes a message from the maintainer that is written to the user’s desktop. Please review the version changes before proceeding.

## Which versions are affected by GHSA-3mpp-xfvh-qh37?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node-ipc` | npm | From 11.0.0 | 12.0.0 |
| `node-ipc` | npm | From 11.0.0 | 12.0.0 |

## How do I fix GHSA-3mpp-xfvh-qh37?

Upgrade node-ipc to 12.0.0 or later.

## Is GHSA-3mpp-xfvh-qh37 being exploited?

There is no known exploitation of GHSA-3mpp-xfvh-qh37 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-3mpp-xfvh-qh37 and fix it if it is affected.

What it is: GHSA-3mpp-xfvh-qh37 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-3mpp-xfvh-qh37 in the wild and no public exploit code.

Affected packages and fixed versions:
- node-ipc (npm): affected from 11.0.0; fixed in 12.0.0
- node-ipc (npm): affected from 11.0.0; fixed in 12.0.0

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-3mpp-xfvh-qh37/ (Markdown: https://insights.sbomify.com/GHSA-3mpp-xfvh-qh37/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-3mpp-xfvh-qh37

---
From sbomify Insights: https://insights.sbomify.com/GHSA-3mpp-xfvh-qh37/
Summaries are generated and may contain mistakes; the official description above is the record.