Third-party access: 25 incidents in the ledger
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
Third-party access is access to a customer's cloud or software-as-a-service data that came through a vendor, supplier, integration or contractor the customer had trusted, so the incident began in the outside party's systems or credentials and reached the customer through a grant already in place.
Open the ledger · All eight paths
How it works
Customers grant outside parties access on purpose: a monitoring company, a data integration, an analytics tool. AWS documentation describes the pattern with a role that trusts another account, and says the external ID in the trust policy is there to prevent the confused deputy problem, in which an entity without permission coerces a more-privileged entity to act for it. The third party often serves many customers from one account, so the trust is shared.
When the vendor is compromised, its access to each customer is the path. The sources in the ledger describe tokens held by an integration, a contractor account or a connected app. The customer's exposure is whatever it granted, which is why the documentation tells owners to scope what a third party can reach and to condition the grant on an identifier that is specific to the customer.
The incidents
| Disclosed | Organization | Cloud | How access was gained |
|---|---|---|---|
| 2026-09-08 | Veradigm Inc. | not public | The filing says a third-party vendor had an incident and an unauthorized party obtained credentials from the vendor’s environment to a company application programming interface, then used them to download patient data; the compromised credentials gave access only through that interface. |
| 2026-07-02 | AdaptHealth Corp. | not public | The filing says a threat actor gained unauthorized access to certain cloud-based business applications (the provider is not named) after a social engineering attack that compromised a user session associated with a third-party contractor. |
| 2026-07-02 | AdaptHealth | not public | The Form 8-K says a threat actor gained unauthorized access to certain cloud-based business applications, and that the incident was the result of a successful social engineering attack that compromised a user session associated with a third-party contractor. |
| 2026-06-23 | 8x8, Inc. | Salesforce | The filing says an unauthorized third party threat actor exploited the Klue third-party application programming integration connected to the company's Salesforce customer relationship management system. |
| 2026-05-08 | SailPoint, Inc. | GitHub | The filing says the company detected unauthorized access to a subset of its GitHub repositories and that the root cause was a vulnerability in a third-party application, which it does not name. |
| 2025-09-02 | Cloudflare | Salesforce | The company stated the threat actor obtained OAuth credentials associated with the Salesloft Drift chat agent's Salesforce integration, and used a stolen credential used by the Salesloft integration to log in to its Salesforce tenant. |
| 2025-08-20 | Salesloft (Drift) | AWS | The investigation summary says the threat actor accessed the Salesloft GitHub account (March to June 2025), then accessed Drift's AWS environment and obtained OAuth tokens for customers' integrations, and used them to access data via Drift integrations. |
| 2025-08-05 | Salesforce | Google stated that the instance was impacted by UNC6040 activity described in the same post, which describes voice phishing in which employees are tricked into authorizing a malicious connected app or sharing credentials. | |
| 2025-03-12 | Salesforce customers (multiple organizations) | Salesforce | Salesforce stated threat actors impersonated IT support by phone, luring customers' employees and third-party support workers to phishing pages to steal credentials and MFA tokens, or to add a malicious connected app. |
| 2024-10-22 | Avaya Holdings Corp. | not public | The SEC press release says the threat actor likely behind the SolarWinds Orion hack accessed the company’s systems without authorization. It describes the access as part of an investigation of public companies potentially impacted by the compromise of SolarWinds’ Orion software. The SEC charged the company over the accuracy of its public disclosure of the incident. |
| 2024-02-01 | Cloudflare | Okta | The company stated the actor used one access token and three service account credentials taken in the October 2023 Okta compromise that the company had failed to rotate. |
| 2023-11-16 | Global Tel*Link Corp. | not public | The FTC press release says that, after the company and a third-party vendor copied the data into the cloud for testing, changes made by the vendor to the security settings left the data accessible via the internet without safeguards, until a security researcher alerted the company. |
| 2023-10-23 | 1Password | Okta | The company stated it detected suspicious activity on its Okta instance used to manage employee-facing apps on September 29, and later confirmed it was a result of the provider’s Support System breach. |
| 2023-10-20 | BeyondTrust | Okta | The company stated it detected an attacker trying to access an in-house Okta administrator account using a valid session cookie stolen from the provider’s support system. |
| 2022-12-31 | Slack | GitHub | The company stated that a limited number of employee tokens were stolen and misused to reach its externally hosted GitHub repository, and that a third-party vendor was compromised. |
| 2022-07-14 | Quoine Pte Ltd | not public | The decision says social engineering of employees of the company's domain registrar led to control of its domain hosting account being handed to an external actor, who redirected the company's mail, reset the password of a DevOps account, and used the reset credentials to reach the company's cloud computing platform, which held API keys to its databases. |
| 2022-05-19 | MGM Resorts International | not public | The OPC finding, relaying MGM's account, says an unauthorized actor logged into a third-party platform used by MGM software developers with an MGM employee's credentials compromised in an earlier unrelated breach, exploited a coding flaw on that platform to bypass multi-factor authentication, found a temporary access token, and used it to reach guest data on an external cloud server for about one hour. |
| 2022-04-15 | Heroku (Salesforce) and Travis CI OAuth tokens | GitHub | Heroku stated that initial access to its environment was obtained by using a compromised token for a Heroku machine account, after which stored customer GitHub integration OAuth tokens were downloaded; GitHub stated the tokens were then abused against GitHub.com. |
| 2022-03-22 | Okta (contractor Sitel) | Okta | The post-mortem says an attacker obtained remote access, using RDP, to a computer owned and managed by Okta's sub-processor Sitel and used by a customer support engineer; the attacker did not take over an Okta account. |
| 2021-04-15 | Codecov | Codecov | The company stated that an error in its Docker image creation process allowed the actor to extract the credential required to modify the Bash Uploader script, which was then altered to send CI environment variables to a third-party server. |
| 2021-03-16 | Mimecast | Microsoft 365 | The company stated the threat actor used the SolarWinds supply-chain compromise to gain access to part of its production grid environment, and from there accessed Mimecast-issued certificates and related connection information; the certificate was then used against a small number of customer Microsoft 365 tenants. |
| 2020-12-15 | Ascension Data & Analytics | not public | The FTC complaint says a vendor hired for text recognition scanning stored the documents on a cloud-based server and a separate cloud-based storage location, misconfigured both, and left the information exposed to anyone on the internet; no password was required. The complaint says the respondent did not assess the vendor's security measures. |
| 2020-12-14 | SolarWinds | Microsoft 365 | The filing says the vulnerability was introduced as a result of a compromise of the Orion software build system, and that the company was made aware of an attack vector used to compromise its Office 365 emails. The Microsoft post says that in actions observed in the Microsoft cloud, attackers gained administrative access either using compromised privileged account credentials (for example stolen passwords) or by forging SAML tokens using compromised token signing certificates. |
| 2020-10-16 | MRI Diagnostics Pte Ltd and Clarity Radiology Pte Ltd | not public | The decision says the clinic subscribed to an internet-based teleradiology system provided by Clarity Radiology, a cloud-based software service, which engaged an overseas vendor to maintain it. The vendor removed access restrictions on a network folder to patch the system and did not restore them, so the spreadsheets were indexed by search engines. |
| 2020-07-11 | LiveAuctioneers | AWS | The company's letter to the Washington Attorney General says a hacker breached one of its third-party software solutions and obtained a source control key, which gave access to its source repository, its cloud-based storage environment and its production database, then used internal users' credentials to download the user database. |
The kind of control that addresses it
grant each vendor a scoped role bound to a customer-specific condition, review integrations on a schedule, and revoke tokens the vendor no longer needs
Related pages
Sources
- AWS IAM User Guide: access to accounts owned by third parties, read 16 Nov 2026
- AWS IAM User Guide: the confused deputy problem, read 16 Nov 2026
- Microsoft Learn: manage application permissions, read 16 Nov 2026
Last reviewed 16 Nov 2026.