
The Old Software Keys That Still Opened Customer Records
Attackers used credentials associated with Gainsight to reach Salesforce customers in 2025. The investigation exposed a mismatch between the lifetime of a digital permission and the evidence available to explain its theft.
The newest credential in a set examined after the Gainsight incident was already more than two years old. The oldest dated to 2017. Yet in late 2025, attackers were using credentials associated with the customer-management software’s Salesforce integration to make requests against corporate customers’ accounts.
That account comes from Gainsight’s January 2026 technical explanation. Old permissions remained useful after the records that might explain their theft had disappeared. Investigators could examine recent activity more readily than the original exposure.
Gainsight sells software used to manage relationships with business customers. Its connection to Salesforce lets separate applications work with information held in the customer relationship platform. An OAuth token is the digital permission enabling that connection. It can allow software to act without a person repeatedly typing a password, making automation convenient and an exposed permission consequential.
On November 20, 2025, Salesforce disabled connections involving Gainsight-published applications. Its security advisory, subsequently updated, says unusual activity may have enabled unauthorized access to some customers’ data. Salesforce said it found no indication of a vulnerability in its own platform. That position addresses the route of entry; it does not erase unauthorized use of a connection to customer information.
Contemporaneous Reuters reporting described the revocation while emphasizing that the news agency could not establish the incident’s scope or nature. The early public record therefore supported a real security response without supplying a reliable total of affected companies or stolen records. A list of integrations under review could not stand in for that missing count.
The investigation’s most revealing difficulty emerged later. Gainsight said Mandiant received a file containing 285 associated tokens from people presenting themselves as threat actors. The company could not establish the source of that set. Its available logs extended back one year, while the tokens were substantially older. Those facts leave room for a historical leak from Gainsight or collection elsewhere; they do not identify the original thief or location.
A separate Mandiant investigation summary, published by Gainsight in December, said the investigators identified no evidence of an active threat actor in Gainsight’s logs. It described credential rotation, stronger access controls, logging and configuration changes. This was a commissioned investigation summarized on the client’s website, with findings tied to its stated period and visibility. It was not a public release of every underlying forensic record.
That qualification matters because different parts of the same software business can have different exposures. CrowdStrike’s published summary covered ancillary application environments, including Skilljar and other Gainsight products. It reported no evidence of unauthorized activity in those environments and said their cloud and code-management environments did not share an identity provider with Customer Success. The corporate name alone did not make every product one compromised system.
Meanwhile, cutting the connection created a second business problem. Gainsight’s November 25 customer update described a team assembled to help customers manage their instances while the Salesforce application was offline. Its chief executive then knew of only a handful of customers whose data had been affected. That was a dated company assessment, not a final independently verified victim count.
The same connection that made customer information usable had become something to suspend. Containment could interrupt legitimate work even for an organization still checking whether its records had been accessed. Customers had to manage both the interruption and the work of checking for unauthorized access.
Salesforce re-enabled the integrations on December 10 after remediation it said Mandiant and CrowdStrike had independently validated. That restored a business capability. It did not settle the origin of the historical credential set. The lasting finding is the mismatch: a permission can remain useful to an attacker longer than the surviving records can explain its first exposure.
Compiled November 16, 2026. Records and findings keep the dates stated in their sources; each link in the text opens the document it relies on.