Skip to content
Cloud Security Breaches

Slack (2022): what the sources say about the cloud incident

Slack disclosed the incident on 31 Dec 2022. What was exposed, as the sources state it: The company stated that private code repositories were downloaded, that they contained no customer data, means to access customer data or Slack's primary codebase, and that the production environment was not accessed.

Open the ledger · Report a correction

Disclosed
31 Dec 2022
Incident window
December 2022 (repositories downloaded 2022-12-27)
Cloud or provider
GitHub
What was exposed
The company stated that private code repositories were downloaded, that they contained no customer data, means to access customer data or Slack's primary codebase, and that the production environment was not accessed.
How access was gained
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.
Access path
Stolen user credentials and session tokens; also Third-party access
Kind of control that addresses it
store source-control tokens in a managed secret store with short lifetimes and IP allow-listing, and alert on token use from unexpected locations

In the words of the source

“Upon investigation, we discovered that a limited number of Slack employee tokens were stolen and misused to gain access to our externally hosted GitHub repository.” (company statement, Slack's security update)

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. Slack's security update, read 16 Nov 2026

Last reviewed 16 Nov 2026.