# GHSA-54pg-9963-v8vg: Compromised version of intercom-client published to npm

> A compromised npm package version executes malicious code during installation, stealing credentials and environment data from developer machines and CI systems.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 May 2026

## What is GHSA-54pg-9963-v8vg?

GHSA-54pg-9963-v8vg is a vulnerability in intercom-client, published on 7 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

### 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

## Which versions are affected by GHSA-54pg-9963-v8vg?

2 open source packages ship an affected version, including intercom-client.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `intercom-client` | npm | All versions | None |
| `intercom-client` | npm | All versions | None |

## How do I fix GHSA-54pg-9963-v8vg?

No fix has been published for GHSA-54pg-9963-v8vg yet. Limit exposure of the affected software until one is available.

## Is GHSA-54pg-9963-v8vg being exploited?

There is no known exploitation of GHSA-54pg-9963-v8vg in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-54pg-9963-v8vg and fix it if it is affected.

What it is: GHSA-54pg-9963-v8vg is a vulnerability in intercom-client, published on 7 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-54pg-9963-v8vg in the wild and no public exploit code.

Affected packages and fixed versions:
- intercom-client (npm): affected all versions; no fix listed
- intercom-client (npm): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-54pg-9963-v8vg/ (Markdown: https://insights.sbomify.com/GHSA-54pg-9963-v8vg/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-54pg-9963-v8vg

---
From sbomify Insights: https://insights.sbomify.com/GHSA-54pg-9963-v8vg/
Summaries are generated and may contain mistakes; the official description above is the record.