Compromised version of intercom-client published to npm

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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…

Published by the source

7 May 2026, 17:32 UTC

Last modified by the source

7 May 2026, 17:46 UTC

Source last checked

26 Oct 2026, 12:51 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-54pg-9963-v8vg

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-54pg-9963-v8vg

3. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-54pg-9963-v8vg

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-54pg-9963-v8vg

Advisory: Compromised version of intercom-client published to npm
IDs: GHSA-54pg-9963-v8vg
Record: https://patchnext.com/advisories/ghsa-54pg-9963-v8vg (revision 3, source checked 26 Oct 2026, 12:51 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm intercom-client: affected >= 7.0.4, <= 7.0.4

## Suggested inspection (read-only)
- `npm ls intercom-client --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on intercom-client.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-54pg-9963-v8vg (GitHub-reviewed advisory GHSA-54pg-9963-v8vg lists affected ranges: npm intercom-client >=7.0.4 <=7.0.4)
- Verified: https://osv.dev/vulnerability/GHSA-54pg-9963-v8vg (OSV record GHSA-54pg-9963-v8vg lists affected ranges: npm intercom-client >=7.0.4 <=7.0.4)

Commands are suggestions: review each one before running it.