# Compromised tag of intercom-php published via GitHub

Advisory record · `GHSA-gr3r-crp5-qrrm`

- **Identifiers:** `GHSA-gr3r-crp5-qrrm` · `PKSA-gwt3-5dgf-97fx`
- **State:** Confirmed
- **Severity:** CVSS 9.3 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-506](https://cwe.mitre.org/data/definitions/506.html)
- **Tags:** [CWE-506](https://agentprime.io/advisories/tag/cwe-506.md)
- **Published:** 7 May 2026
- **Updated:** 7 May 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 7 May 2026, 16:48 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.3: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `intercom/intercom-php` (Packagist): affected `=5.0.2`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Packagist package intercom/intercom-php version 5.0.2 was published with a malicious Composer plugin that downloaded a JavaScript runtime and harvested credentials. The malicious tag was live for about two hours on April 30, 2026, and has since been reverted; the source lists no fixed version for 5.0.2. Projects that installed 5.0.2 in that window should treat accessible credentials as compromised and rotate them, and use version 5.0.1 instead.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.3 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 14:25 UTC: First seen by agentprime
- 31 Oct 2026, 14:25 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-gr3r-crp5-qrrm)

## Sources

- [GitHub Advisory Database: GHSA-gr3r-crp5-qrrm](https://github.com/advisories/GHSA-gr3r-crp5-qrrm)
- [OSV: GHSA-gr3r-crp5-qrrm](https://osv.dev/vulnerability/GHSA-gr3r-crp5-qrrm)
- <https://github.com/intercom/intercom-php/security/advisories/GHSA-gr3r-crp5-qrrm>
- <https://github.com/intercom/intercom-php>
- <https://www.intercomstatus.com/us-hosting/incidents/01KQFN6VS6ARP1XBR1K1SBYY59>
- <https://www.wiz.io/blog/mini-shai-hulud-supply-chain-sap-npm>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-gr3r-crp5-qrrm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-gr3r-crp5-qrrm/>. Everything for agents: <https://agentprime.io/llms.txt>.