GHSA-gr3r-crp5-qrrm: Intercom/intercom php Compromised Tag Of Intercom-php Published Vulnerability

CRITICAL
CVSS 9.3
CWE-506
Published
Advisory Summary

GHSA-gr3r-crp5-qrrm is a CRITICAL (CVSS 9.3) compromised tag of intercom-php published vulnerability (CWE-506: Embedded Malicious Code) affecting Intercom/intercom php libraries in the Packagist ecosystem. The issue involves compromised tag of intercom-php published via github. Remediation is available in the latest vendor maintenance releases.

GHSA-gr3r-crp5-qrrm at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-gr3r-crp5-qrrm
Severity CRITICAL
CVSS v3.1 Base Score 9.3
CWE Classification CWE-506: Embedded Malicious Code
Affected Product Intercom/intercom php
Package Ecosystem Packagist
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-gr3r-crp5-qrrm

To remediate this vulnerability, upgrade all affected Intercom/intercom php 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/intercom-php fixed: Latest secure release
Upgrade intercom/intercom-php to 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:

inspect dependencies for intercom/intercom-php

How to Check if You Are Affected

To determine whether your application is affected by GHSA-gr3r-crp5-qrrm, inspect your project dependencies for Intercom/intercom php:

inspect dependencies for intercom/intercom-php

Analyze the terminal output to locate any version of Intercom/intercom php 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: Verify declared build manifests and deployed runtime container environments.

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/intercom php, 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, a malicious commit was pushed to the intercom/intercom-php repository and tagged as version 5.0.2, using a compromised service account (github-management-service). This occurred as part of the same supply chain attack that affected intercom-client on npm. The malicious version contained a Composer plugin that acted as a dropper, downloading the Bun JavaScript runtime (version 1.3.13) and executing an obfuscated credential-harvesting payload. The payload targeted cloud provider credentials (AWS, GCP, Azure), environment variables, .env files, SSH keys, local configuration files, and CI/CD secrets. The malicious tag was live between approximately 20:53 UTC and 22:37 UTC on April 30, 2026, before being identified and reverted to a clean commit. This compromise is part of the "Mini Shai-Hulud" supply chain campaign tracked by Wiz and Socket. To check if a consuming project is affected, run: `composer show intercom/intercom-php --version`. If the project installed or updated between 20:53 and 22:37 UTC on April 30, it may have received the malicious version. The malicious commit hash was `e69bf4b3`. The clean commit is `9371eba9`. Check `composer.lock` to verify which version the consuming project is using. ### Patches Version 5.0.1 and all prior versions are unaffected. The 5.0.2 tag has been reverted to a clean commit. Downgrade to 5.0.1 or run `composer clear-cache` and reinstall to get the clean 5.0.2. ### Workarounds If a project installed version 5.0.2 during the affected window, treat all credentials accessible from that environment as compromised and rotate them. Clear the Composer cache with `composer clear-cache` and check `composer.lock` for the commit hash to confirm whether you have the malicious or clean version. ### Resources - https://www.intercomstatus.com/us-hosting/incidents/01KQFN6VS6ARP1XBR1K1SBYY59 - https://www.wiz.io/blog/mini-shai-hulud-supply-chain-sap-npm

GHSA-gr3r-crp5-qrrm Affected Intercom/intercom php Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
intercom/intercom-php
Packagist
5.0.2
All 1 versions
5.0.2
None specified

References

Frequently Asked Questions

What is GHSA-gr3r-crp5-qrrm?
GHSA-gr3r-crp5-qrrm is a security vulnerability in Intercom/intercom php involving Compromised tag of intercom-php published via GitHub under CWE-506: Embedded Malicious Code.
Which Intercom/intercom php versions are affected?
Affected versions include releases prior to current release patches across affected packages: intercom/intercom-php.
What version fixes GHSA-gr3r-crp5-qrrm?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is intercom/intercom-php affected?
Yes, intercom/intercom-php 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-gr3r-crp5-qrrm?
GHSA-gr3r-crp5-qrrm 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-gr3r-crp5-qrrm?
GHSA-gr3r-crp5-qrrm is classified under CWE-506: Embedded Malicious Code (The product contains code that appears to be malicious in nature.).
How can I check Packagist dependencies for GHSA-gr3r-crp5-qrrm?
Run the dependency tree command: 'inspect dependencies for intercom/intercom-php'. 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-gr3r-crp5-qrrm",
  "modified" : "2026-05-07T16:48:41Z",
  "published" : "2026-05-07T16:48:41Z",
  "aliases" : [ ],
  "summary" : "Compromised tag of intercom-php published via GitHub",
  "details" : "### Impact\n\nOn April 30, 2026, a malicious commit was pushed to the intercom/intercom-php repository and tagged as version 5.0.2, using a compromised service account (github-management-service). This occurred as part of the same supply chain attack that affected intercom-client on npm.\n\nThe malicious version contained a Composer plugin that acted as a dropper, downloading the Bun JavaScript runtime (version 1.3.13) and executing an obfuscated credential-harvesting payload. The payload targeted cloud provider credentials (AWS, GCP, Azure), environment variables, .env files, SSH keys, local configuration files, and CI/CD secrets.\n\nThe malicious tag was live between approximately 20:53 UTC and 22:37 UTC on April 30, 2026, before being identified and reverted to a clean commit.\n\nThis compromise is part of the \"Mini Shai-Hulud\" supply chain campaign tracked by Wiz and Socket.\n\nTo check if a consuming project is affected, run: `composer show intercom/intercom-php --version`. If the project installed or updated between 20:53 and 22:37 UTC on April 30, it may have received the malicious version. The malicious commit hash was `e69bf4b3`. The clean commit is `9371eba9`. Check `composer.lock` to verify which version the consuming project is using.\n\n### Patches\n\nVersion 5.0.1 and all prior versions are unaffected. The 5.0.2 tag has been reverted to a clean commit. Downgrade to 5.0.1 or run `composer clear-cache` and reinstall to get the clean 5.0.2.\n\n### Workarounds\n\nIf a project installed version 5.0.2 during the affected window, treat all credentials accessible from that environment as compromised and rotate them. Clear the Composer cache with `composer clear-cache` and check `composer.lock` for the commit hash to confirm whether you have the malicious or clean version.\n\n### Resources\n\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" : "Packagist",
      "name" : "intercom/intercom-php"
    },
    "versions" : [ "5.0.2" ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/intercom/intercom-php/security/advisories/GHSA-gr3r-crp5-qrrm"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/intercom/intercom-php"
  }, {
    "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-07T16:48:41Z",
    "nvd_published_at" : null
  }
}