Slack is a workplace messaging platform whose integrations, permissions, and exposed data can affect organizational security and privacy.
Search across headline titles and summaries.
Background for this topic.
Slack is a hosted collaboration platform for workplace channels, direct messages, file sharing, and integrations with other services. It is security-relevant because workspaces can contain confidential discussions, credentials, personal data, and operational documents. Unauthorized account access, overly broad channel or guest permissions, and accidental external sharing can expose that content; retention settings may also determine how much information remains available after an incident.
Key attack surfaces include identity and session controls, OAuth applications, bots, webhooks, APIs, and Slack’s desktop, mobile, and browser clients. Security teams should enforce strong authentication, review app permissions and tokens, restrict external access, patch clients, and use audit logs and appropriate retention or data-loss controls. Advisories about client or API vulnerabilities should be assessed for affected versions, required access, and potential reach into workspace data. Investigations may need to examine application tokens, integration activity, and audit records as well as user credentials.
A single poisoned notification from WhatsApp, Slack, SMS, Signal, Instagram, or Messenger could have hijacked Google Gemini's voice assistant on Android and made it open a victim's connected windows, fake a message from their boss, push the phone into a Zoom call, or quietly poison its long-term memory