VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

node-ipc: vulnerability history, versions and safety

node-ipc is a package in the npm ecosystem. Vulert records 4 vulnerabilities for it across 76 releases, from Mar 2022 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded C2 L2
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 14 May 2026.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in npm →

See all node-ipc vulnerabilities

Vulert verdict on node-ipc 14.0.0 i

Updated on 23 Oct 2026

Careful: 14.0.0 was published with malicious code in it, not just a bug. Do not install it.

Package health score 15/100
  • Security Malicious code published
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

The current release contains malicious code, which caps this score.

What to do: Do not resolve 14.0.0 as-is. Check whether you already run an affected release and pin a version the maintainers have re-published. Check what you run: Vulert alerts you when a safe version is published. Monitor it with Vulert →

  • Current release 14.0.0 — affected i
  • Vulnerabilities on record 4 over 4 years · 1 in the last year i
  • Latest disclosure 14 May 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 2 i
  • Malicious packages 1 i
  • Depended on by 17 packages i
  • Stars 66 i
  • OpenSSF scorecard 5/10 i
  • Last release 1 month ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for node-ipc, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
14.0.0 24 Aug 2026 C1 L1 malicious MIT No Details →
12.0.0 12 Aug 2024 C1 L1 malicious MIT No Details →
11.1.0 15 Mar 2022 C1 L2 malicious MIT No Details →
11.0.0 08 Mar 2022 C1 L2 malicious MIT No Details →
10.1.0 15 Sep 2021 C1 L1 malicious MIT No Details →
10.0.2 07 Jul 2021 C1 L1 malicious MIT No Details →
10.0.1 04 Jul 2021 C1 L1 malicious MIT No Details →
10.0.0 04 Jul 2021 C1 L1 malicious MIT No Details →
9.2.1 02 Jul 2021 C1 L1 malicious MIT No Details →
9.2.0 01 Jul 2021 C1 L1 malicious MIT No Details →
9.1.5 01 Jul 2021 C1 L1 malicious MIT No Details →
9.1.4 26 Feb 2021 C1 L1 malicious MIT No Details →
9.1.3 12 Nov 2020 C1 L1 malicious MIT No Details →
9.1.2 11 Nov 2020 C1 L1 malicious MIT No Details →
9.1.1 25 Aug 2017 C1 L1 malicious non-standard No Details →
9.1.0 21 Jul 2017 C1 L1 malicious non-standard No Details →
9.0.1 16 Apr 2017 C1 L1 malicious non-standard No Details →
9.0.0 16 Apr 2017 C1 L1 malicious non-standard No Details →
8.10.3 14 Feb 2017 C1 L1 malicious non-standard No Details →
8.10.2 22 Dec 2016 C1 L1 malicious non-standard No Details →
8.10.1 22 Dec 2016 C1 L1 malicious non-standard No Details →
8.10.0 22 Dec 2016 C1 L1 malicious non-standard No Details →
8.9.3 20 Dec 2016 C1 L1 malicious non-standard No Details →
4.1.1 07 Oct 2016 C1 L1 malicious non-standard No Details →
5.2.1 07 Oct 2016 C1 L1 malicious non-standard No Details →
6.0.3 07 Oct 2016 C1 L1 malicious non-standard No Details →
7.0.3 07 Oct 2016 C1 L1 malicious non-standard No Details →
7.0.2 07 Oct 2016 C1 L1 malicious non-standard No Details →
8.9.2 06 Oct 2016 C1 L1 malicious non-standard No Details →
8.9.1 06 Oct 2016 C1 L1 malicious non-standard No Details →
8.9.0 03 Oct 2016 C1 L1 malicious non-standard No Details →
8.8.0 30 Sep 2016 C1 L1 malicious non-standard No Details →
8.1.1 12 Aug 2016 C1 L1 malicious non-standard No Details →
8.1.0 02 Aug 2016 C1 L1 malicious non-standard No Details →
8.0.0 14 Jul 2016 C1 L1 malicious non-standard No Details →
7.0.0 23 Mar 2016 C1 L1 malicious non-standard No Details →
6.0.2 16 Mar 2016 C1 L1 malicious non-standard No Details →
6.0.0 11 Jan 2016 C1 L1 malicious non-standard No Details →
5.2.0 04 Jan 2016 C1 L1 malicious non-standard No Details →
5.1.0 22 Dec 2015 C1 L1 malicious non-standard No Details →
5.0.0 10 Dec 2015 C1 L1 malicious non-standard No Details →
4.1.0 03 Dec 2015 C1 L1 malicious non-standard No Details →
4.0.0 02 Dec 2015 C1 L1 malicious non-standard No Details →
3.0.0 27 Sep 2015 C1 L1 malicious non-standard No Details →
2.0.2 27 Sep 2015 C1 L1 malicious non-standard No Details →
2.0.0 23 Aug 2015 C1 L1 malicious non-standard No Details →
1.2.2 27 Jul 2015 C1 L1 malicious non-standard No Details →
1.2.1 24 Jul 2015 C1 L1 malicious non-standard No Details →
1.2.0 24 Jul 2015 C1 L1 malicious non-standard No Details →
1.1.13 09 Dec 2014 C1 L1 malicious non-standard No Details →
1.1.12 27 Sep 2014 C1 L1 malicious non-standard No Details →
1.1.11 06 Sep 2014 C1 L1 malicious non-standard No Details →
1.1.10 06 Sep 2014 C1 L1 malicious non-standard No Details →
1.1.9 05 Sep 2014 C1 L1 malicious non-standard No Details →
1.1.8 05 Sep 2014 C1 L1 malicious non-standard No Details →
1.1.7 04 Sep 2014 C1 L1 malicious non-standard No Details →
1.1.6 03 Sep 2014 C1 L1 malicious non-standard No Details →
1.1.5 31 Aug 2014 C1 L1 malicious non-standard No Details →
1.1.4 31 Aug 2014 C1 L1 malicious non-standard No Details →
1.1.0 28 Aug 2014 C1 L1 malicious non-standard No Details →
1.0.5 08 May 2014 C1 L1 malicious non-standard No Details →
1.0.0 11 Mar 2014 C1 L1 malicious non-standard No Details →
0.9.16 04 Mar 2014 C1 L1 malicious non-standard No Details →
0.9.15 03 Mar 2014 C1 L1 malicious non-standard No Details →
0.9.14 02 Mar 2014 C1 L1 malicious non-standard No Details →
0.9.13 01 Mar 2014 C1 L1 malicious non-standard No Details →
0.9.11 01 Mar 2014 C1 L1 malicious non-standard No Details →
0.9.10 01 Mar 2014 C1 L1 malicious non-standard No Details →
0.9.9 01 Mar 2014 C1 L1 malicious non-standard No Details →
0.9.8 01 Mar 2014 C1 L1 malicious non-standard No Details →
0.9.7 28 Feb 2014 C1 L1 malicious non-standard No Details →
0.9.6 28 Feb 2014 C1 L1 malicious non-standard No Details →
0.9.5 27 Feb 2014 C1 L1 malicious non-standard No Details →
0.9.0 26 Feb 2014 C1 L1 malicious non-standard No Details →
0.0.2 22 Feb 2014 C1 L1 malicious non-standard No Details →
0.0.1 22 Feb 2014 C1 L1 malicious non-standard No Details →

All 76 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 3
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for node-ipc

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2022-23812: Embedded Malicious Code in node-ipc 9.8 critical 10.1.3 16 Mar 2022
Vulnerability in node-ipc: node-ipc behavior change N/A low 12.0.0 16 Mar 2022
Hidden functionality vulnerability in node-ipc N/A low No fix published 16 Mar 2022
Critical Malicious Code Injection in node-ipc Package N/A critical No fix published 14 May 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About node-ipc

Is node-ipc safe to use?

Vulert records 4 vulnerabilities for node-ipc in npm: 2 critical, 0 high, 0 medium and 2 low. 2 of them have no published fix yet, so those are the ones to avoid or mitigate. 1 are malicious-package vulnerabilities: the published package itself contained hostile code, not only a bug.

What is node-ipc's Vulert package health score?

Vulert scores node-ipc 15/100, which reads as critical. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release contains malicious code, which caps this score.

Is the latest version of node-ipc affected?

Yes. 14.0.0, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of node-ipc should I use?

14.0.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does node-ipc have?

4 vulnerabilities are recorded for node-ipc in the npm ecosystem: 2 critical, 0 high, 0 medium and 2 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new node-ipc vulnerabilities disclosed?

1 vulnerability was recorded for node-ipc in the last 12 months, and the oldest entry in this database dates to 16 Mar 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of node-ipc are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

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.