Vulnerability Database · npm · node-ipc · Version
node-ipc 6.0.0
6.0.0 is affected by 2 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 14.0.0.
Critical 1 High 0 Medium 0 Low 1 Unrated 0
-
Released 11 Jan 2016
Licence non-standard
Also known from other sources 0
Newer releases 76
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
node-ipc 6.0.0 vulnerabilities
2 vulnerabilities cover node-ipc 6.0.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Critical Malicious Code Injection in node-ipc Package | N/A critical | No fix published | 14 May 2026 |
| Hidden functionality vulnerability in node-ipc | N/A low | No fix published | 16 Mar 2022 |
Looking for another version, or everything Vulert holds for node-ipc?
Questions
About node-ipc 6.0.0
Is node-ipc 6.0.0 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover node-ipc 6.0.0: 1 critical, 0 high, 0 medium and 1 low. The upgrade Vulert recommends is 14.0.0, and each entry above names the fixed version to move to.
Which version of node-ipc should I use instead of 6.0.0?
14.0.0 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 6.0.0 the latest release of node-ipc?
No. 6.0.0 was published 11 Jan 2016, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
What does a malicious-package vulnerability mean?
It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.
How do I monitor node-ipc for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the node-ipc version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.