node-ipc behavior changeGHSA-3mpp-xfvh-qh37
Fix: RIAEvangelist/node-ipc@a98efaeGHSA-3mpp-xfvh-qh37 is a security vulnerability in node-ipc. A fix is available for node-ipc — see the affected versions and patch details below.
Real-World Exposure
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.
node-ipcnpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | node-ipc | ≥ 11.0.0&&< 12.0.0 | 12.0.0npm install node-ipc@12.0.0 |
Detection & mitigation playbook
Open-source dependencyDetect
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.
Fix
Update node-ipc to 12.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3mpp-xfvh-qh37 is resolved across your whole dependency graph.
Workarounds
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.
Frequently Asked Questions
Is GHSA-3mpp-xfvh-qh37 in your dependencies?
Find it across npm, including transitive dependencies.