Skip to content
Cloud Security Breaches

Heroku (Salesforce) and Travis CI OAuth tokens (2022): what the sources say about the cloud incident

Heroku (Salesforce) and Travis CI OAuth tokens disclosed the incident on 15 Apr 2022. The ledger reads the access path as third-party access with leaked access keys and secrets. The cloud or provider involved: GitHub. Every field rests on the primary sources listed below.

Open the ledger · Report a correction

Disclosed
15 Apr 2022
Incident window
April 2022 (Heroku: 2022-04-07 to 2022-04-13)
Cloud or provider
GitHub
What was exposed
GitHub stated that stolen OAuth user tokens issued to Heroku and Travis CI were used to download data from dozens of organizations, including npm; Heroku stated the actor also downloaded stored customer GitHub integration tokens and a database of pipeline-level config variables.
How access was gained
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.
Access path
Third-party access; also Leaked access keys and secrets
Kind of control that addresses it
scope and shorten the lifetime of machine-account and integration tokens, store third-party OAuth tokens encrypted with separate keys, and prefer sender-constrained tokens

In the words of the source

“We began investigating how the threat actor gained initial access to the environment and determined it was obtained by leveraging a compromised token for a Heroku machine account.” (company statement, April 2022 Incident Review)

Primary sources

If a field is wrong or a newer primary source exists, write to the editor with the entry name in the subject.

Sources

  1. April 2022 Incident Review, read 16 Nov 2026
  2. Security alert: Attack campaign involving stolen OAuth user tokens issued to two third-party integrators, read 16 Nov 2026

Last reviewed 16 Nov 2026.