Vulnerabilities in pkg:npm/intercom-client

PACKAGE
Advisory Summary

GHSA-54pg-9963-v8vg is a CRITICAL (CVSS 9.3) compromised version of intercom-client published vulnerability (CWE-506: Embedded Malicious Code) affecting Intercom client libraries in the npm ecosystem. The issue involves compromised version of intercom-client published to npm. Remediation is available in the latest vendor maintenance releases.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/intercom-client

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/intercom-client. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-54pg-9963-v8vg - CRITICAL Compromised version of intercom-client published to npm

GHSA-54pg-9963-v8vg at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-54pg-9963-v8vg
Severity CRITICAL
CVSS v3.1 Base Score 9.3
CWE Classification CWE-506: Embedded Malicious Code
Affected Product Intercom client
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 9.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix GHSA-54pg-9963-v8vg

To remediate this vulnerability, upgrade all affected Intercom client dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

intercom-client fixed: Latest secure release
npm install intercom-client@Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls intercom-client

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-54pg-9963-v8vg, inspect your project dependencies using npm:

npm ls intercom-client

Analyze the terminal output to locate any version of Intercom client in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The npm ls intercom-client command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-506: Embedded Malicious Code, where the product contains code that appears to be malicious in nature. In Intercom client, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact On April 30, 2026, version 7.0.4 of intercom-client was published to npm using credentials obtained from a compromised developer account. This version was not produced by Intercom's build pipeline. The malicious version contained an obfuscated JavaScript payload that executed during package installation via a preinstall hook. The payload harvested credentials from the environment in which it ran, including cloud provider credentials (AWS, GCP, Azure), environment variables, .env files, GitHub and npm tokens, SSH keys, local configuration files, and cloud metadata service credentials. Harvested data was exfiltrated to attacker-controlled GitHub repositories. The package was live on npm for approximately 2 hours (15:00-17:00 UTC). This compromise is part of the "Mini Shai-Hulud" supply chain campaign tracked by Wiz and Socket. Developers can check if their projects are affected by running: `npm list intercom-client`. If it shows 7.0.4, the project is affected. ### Patches Version 7.0.3 and all prior versions are unaffected. Downgrade to 7.0.3 immediately. ### Workarounds If a developer installed version 7.0.4 on any machine or CI system, treat all credentials accessible from that environment as compromised and rotate them. Check lock files (`package-lock.json`, `yarn.lock`, `pnpm-lock.yaml`) for references to 7.0.4. Review CI/CD build logs for any `npm install` that resolved to 7.0.4 between 15:00 and 17:00 UTC on April 30, 2026. ### Resources - https://socket.dev/blog/intercom-s-npm-package-compromised-in-supply-chain-attack - https://www.intercomstatus.com/us-hosting/incidents/01KQFN6VS6ARP1XBR1K1SBYY59 - https://www.wiz.io/blog/mini-shai-hulud-supply-chain-sap-npm

GHSA-54pg-9963-v8vg Affected Intercom client Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
intercom-client
npm
7.0.4
All 1 versions
7.0.4
None specified

References

Frequently Asked Questions

What is GHSA-54pg-9963-v8vg?
GHSA-54pg-9963-v8vg is a security vulnerability in Intercom client involving Compromised version of intercom-client published to npm under CWE-506: Embedded Malicious Code.
Which Intercom client versions are affected?
Affected versions include releases prior to current release patches across affected packages: intercom-client.
What version fixes GHSA-54pg-9963-v8vg?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is intercom-client affected?
Yes, intercom-client is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of GHSA-54pg-9963-v8vg?
GHSA-54pg-9963-v8vg has a CVSS v3.1 base score of 9.3 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N.
What CWE is associated with GHSA-54pg-9963-v8vg?
GHSA-54pg-9963-v8vg is classified under CWE-506: Embedded Malicious Code (The product contains code that appears to be malicious in nature.).
How can I check npm dependencies for GHSA-54pg-9963-v8vg?
Run the dependency tree command: 'npm ls intercom-client'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-54pg-9963-v8vg",
  "modified" : "2026-05-07T17:32:48Z",
  "published" : "2026-05-07T17:32:48Z",
  "aliases" : [ ],
  "summary" : "Compromised version of intercom-client published to npm",
  "details" : "### Impact\n\nOn April 30, 2026, version 7.0.4 of intercom-client was published to npm using credentials obtained from a compromised developer account. This version was not produced by Intercom's build pipeline.\n\nThe malicious version contained an obfuscated JavaScript payload that executed during package installation via a preinstall hook. The payload harvested credentials from the environment in which it ran, including cloud provider credentials (AWS, GCP, Azure), environment variables, .env files, GitHub and npm tokens, SSH keys, local configuration files, and cloud metadata service credentials.\n\nHarvested data was exfiltrated to attacker-controlled GitHub repositories. The package was live on npm for approximately 2 hours (15:00-17:00 UTC).\n\nThis compromise is part of the \"Mini Shai-Hulud\" supply chain campaign tracked by Wiz and Socket.\n\nDevelopers can check if their projects are affected by running: `npm list intercom-client`. If it shows 7.0.4, the project is affected.\n\n### Patches\n\nVersion 7.0.3 and all prior versions are unaffected. Downgrade to 7.0.3 immediately.\n\n### Workarounds\n\nIf a developer installed version 7.0.4 on any machine or CI system, treat all credentials accessible from that environment as compromised and rotate them. Check lock files (`package-lock.json`, `yarn.lock`, `pnpm-lock.yaml`) for references to 7.0.4. Review CI/CD build logs for any `npm install` that resolved to 7.0.4 between 15:00 and 17:00 UTC on April 30, 2026.\n\n### Resources\n\n- https://socket.dev/blog/intercom-s-npm-package-compromised-in-supply-chain-attack\n- https://www.intercomstatus.com/us-hosting/incidents/01KQFN6VS6ARP1XBR1K1SBYY59\n- https://www.wiz.io/blog/mini-shai-hulud-supply-chain-sap-npm",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "intercom-client"
    },
    "versions" : [ "7.0.4" ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/intercom/intercom-node/security/advisories/GHSA-54pg-9963-v8vg"
  }, {
    "type" : "ADVISORY",
    "url" : "https://github.com/advisories/GHSA-4594-wxqv-j3pm"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/intercom/intercom-node"
  }, {
    "type" : "WEB",
    "url" : "https://socket.dev/blog/intercom-s-npm-package-compromised-in-supply-chain-attack"
  }, {
    "type" : "WEB",
    "url" : "https://www.intercomstatus.com/us-hosting/incidents/01KQFN6VS6ARP1XBR1K1SBYY59"
  }, {
    "type" : "WEB",
    "url" : "https://www.wiz.io/blog/mini-shai-hulud-supply-chain-sap-npm"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-506" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-07T17:32:48Z",
    "nvd_published_at" : null
  }
}