ShinyHunters Claims Theft of Data for 275 Million Canvas Users
ShinyHunters says it stole data for 275 million Instructure Canvas users, uploading 3.65 TB of files. Learn the breach timeline, impact, and mitigation steps.

TL;DR
ShinyHunters uploaded 3.65 TB of data on May 3, alleging a breach that exposed personal information for 275 million Canvas users across almost 9,000 schools.
Context Instructure, the provider of the Canvas learning‑management system, reported a service disruption on April 30. By May 1 the company confirmed a “cybersecurity incident” caused by a criminal threat actor. Instructure said it patched vulnerable components, revoked compromised credentials, and rotated API keys within 48 hours.
Key Facts - The hacker collective ShinyHunters claimed responsibility and posted 3.65 TB of stolen files to its public leak site on May 3. - The group says the data set covers 275 million users – students, teachers and staff – at roughly 9,000 educational institutions worldwide. - Stolen items include names, email addresses, student IDs, and private messages exchanged on Canvas. Instructure confirmed that passwords and other private credentials were not taken. - ShinyHunters also alleges access to Instructure’s Salesforce CRM instance, suggesting the breach extended beyond the LMS. - The breach follows a series of high‑profile attacks by the same group, including incidents at Panera Bread, ADT, Crunchyroll, Bumble, and Rockstar Games earlier this year.
What It Means The scale of the alleged exfiltration makes this one of the largest education‑sector breaches on record. Even without passwords, the combination of personal identifiers and private communications creates a rich dataset for phishing, credential‑stuffing, and social‑engineering campaigns. Schools may face increased spam, targeted scams, and reputational damage.
Mitigations - Patch promptly: Apply the latest security updates for Canvas, especially those addressing API authentication and token handling. Check Instructure’s advisory for CVE identifiers linked to the incident. - Rotate secrets: Replace all API keys, OAuth tokens, and service‑account passwords. Enforce short‑lived tokens where possible. - Monitor for abuse: Deploy detection rules for MITRE ATT&CK techniques T1078 (Valid Accounts) and T1566 (Phishing). Look for anomalous API calls and mass‑export patterns. - Secure communications: Enable end‑to‑end encryption for in‑app messaging or migrate sensitive conversations to a separate, hardened platform. - Educate users: Conduct phishing awareness training for students and staff, emphasizing the risk of unsolicited messages that reference Canvas content. - Audit third‑party integrations: Review Salesforce and other connected services for over‑privileged access and enforce least‑privilege principles.
What to Watch Next Watch for Instructure’s forthcoming forensic report, which should clarify the exploited vulnerability and confirm whether additional data—such as backup files—were accessed. Security teams should prepare to respond to any follow‑up phishing campaigns that leverage the leaked information.
Continue reading
More in this thread
Florida Man Arrested for Allegedly Harvesting Private Data via TikTok Video
Peter Olaleru
Florida Man Charged After Using TikTok to Reveal Victims’ Private Data
Peter Olaleru
Law Firm Investigates Hematology Oncology Consultants After RHYSIDA Ransomware Exposes Patient Data
Peter Olaleru
Conversation
Reader notes
Loading comments...