Instructure, the company behind the Canvas learning management system, is dealing with a two-stage extortion attack by ShinyHunters. On May 7 the group replaced Canvas login pages with a ransom message. Classes and final exams were disrupted at universities and school districts in North America, Europe and Asia-Pacific.
What happened
Instructure says attackers gained access to Canvas systems around April 25. It detected the intrusion around April 29 and disclosed it on May 1. Instructure later confirmed that the attackers abused its Free-For-Teacher programme, which let educators create accounts without verification by their institution. Stolen data includes names, email addresses, student ID numbers and messages between users. The company said it found no evidence that passwords, dates of birth, government IDs or financial data were involved.
ShinyHunters claimed responsibility on May 3 and set a payment deadline. After Instructure said the incident was contained, the group struck again on May 7 and defaced login portals. Instructure took Canvas and its test environments offline, then restored service after shutting down the Free-For-Teacher programme. On May 11 the company said it had reached an agreement with the attackers and had received confirmation that the data was destroyed. It did not disclose the terms.
Impact
- ShinyHunters claims 3.65 TB of data covering about 275 million users at nearly 9,000 institutions. These figures are unverified, and the group has exaggerated before.
- Institutions in the US, Canada, Australia, New Zealand, the Netherlands, Hong Kong and Singapore restricted or temporarily disabled Canvas.
- A proposed class action was filed in federal court in California, and the US House Homeland Security Committee asked Instructure for a briefing.
Recommendations
- Schools should warn students and staff about phishing that uses the incident as a lure or quotes real course messages.
- Review and remove any Canvas LTI integrations, API tokens and admin accounts that are not strictly needed, and rotate developer keys.
- Ask SaaS providers whether self-service or unverified account types can reach shared infrastructure, and restrict them where possible.
- Paying a ransom does not guarantee deletion. Plan breach notifications as if the data may still surface.