Slack Hackers Slackers
summary
Slack breaches recur because attackers harvest chat history, abuse apps and sessions, and exploit culture not bugs: attackers buy a Slack session cookie for $10, use that persistent web session to join IT channels, reset SSO credentials and exfiltrate source code (EA/Uber/Twitter examples) or post ransom notes; Slack has ~2,400 apps with ~10% official authors, channel defaults are public, and Audit Logs off by default and costly so defenses rely on exports and scripted backups plus default channels are public and tighter app approvals.
AI-written summary · about
chapters (13)
- 0:00Introduction and speaker background
- 1:28Why Slack is a prime target
- 6:49Slack culture and security risks
- 11:08Real-world Slack attack examples
- 16:23How attackers exploit Slack
- 20:20The danger of Slack apps
- 23:10Ransomware and data destruction risks
- 25:45Mitigation and cultural changes
- 29:23Technical security controls for Slack
- 31:31Audit logs and forensic readiness
- 36:37Incident response and backups
- 38:02Next steps for Slack security
- 39:47Q&A on Teams and Slack differences
related talks
28mSlack App Security: Securing Your Workspaces From a Bot Uprising
55mAttacking Modern Web Technologies
41mHackers vs. Devs - Attacking Dev Tools and Infrastructure
26mBuilding Secure Cultures
30mHow to hack a web app?
28mCyberespionage: Targeted Attacks Abusing Third-Party Cloud Services
46mHow to hack a node app?
12mAre Users Able to Take Control of Their Data?
