Canvas breach: one vendor, thousands of schools offline
When an attacker came back on 7 May, Instructure took Canvas offline for every school on it at once. What schools and training providers should check.
Published · 4 min read

On 7 May, during exam season, Instructure took its Canvas learning platform offline. An attacker it had detected and shut out on 29 April had come back through a second weakness and changed pages that some students and teachers saw once they had logged in. Canvas is used by thousands of schools around the world, Bloomberg reported, and taking it offline took it from all of them at once: Southern Methodist University pushed its Friday exams to Sunday. ShinyHunters, a group known for stealing data and then demanding payment, said it was responsible.
Instructure says the data involved includes usernames, email addresses, course names, enrolment information and messages, and that course content, submissions and credentials were not compromised. The group claimed far more, according to a threat-intelligence brief cited by the law firm Robinson+Cole: 3.654 TB covering about 275 million people at 9,000 institutions. Instructure's own incident page gives no count. On 11 May the company said it had reached an agreement with the attacker, that the data had been returned, and that it had received "digital confirmation of data destruction (shred logs)". I would not put much weight on a deletion log from the people who took the data: nobody else can check it. Then the waiting began. Instructure's chief executive wrote on 26 May that the breakdown for each institution would be "measured in weeks and months, not days", and it was 29 September before the company said its forensic review was complete.
One platform, one door, thousands of schools
That concentration is the point of a platform: one company runs the servers and the security, so thousands of schools get what none could build alone. It is also why one incident reached all of them on the same day, on the vendor's timetable. No school can hurry another company's forensic review. It can only decide in advance how it will run while it waits.
One detail deserves every school's attention. Both times, Instructure says, the attacker used an account on Canvas Free-for-Teacher, its free tier for teachers, and a weakness in that tier's support tickets was exploited too. It was a door no school had any say over, on the platform all of them were using. Instructure has since closed the free tier for good.
What it means for a school or training provider here
In the Philippines, a school that keeps its records on a platform still answers for them. Under the NPC's breach rules, Circular 16-03, the duty to notify stays with the organisation that controls the data even when the processing is outsourced. If a breach involves 100 people or more, the circular allows no delay: the NPC is told within 72 hours on the information available, and the full report follows within five days. A vendor that needs months to say what was taken does not move that clock.
Messages deserve a line of their own. They are where a student might explain a late assignment, or a parent raise a problem at home. They are personal data, and on Canvas they were among the data involved.
When I build a system, it lives in the client's own accounts, with its data in the client's own infrastructure. I would still not tell a school to build its own learning platform: for most, buying one is right, for the reasons in buy something instead. But a school should know which of its records sit with which vendor.
Five checks before the next exam week
- List every platform that holds student or trainee data and what each one holds, messages included, and put them in your Data Privacy Act inventory.
- Ask each vendor how it will tell you about an incident, and whom. Instructure delivered each school's data only to the security contacts that school had named, so name yours before you need them.
- Keep a way to run exam week without the platform: class lists, schedules and assessments exported somewhere you control, and a plan for telling students where to go.
- Write a vendor's incident into your breach plan as a case of its own, with the 72-hour clock and the name of whoever files with the NPC.
- Warn students and parents that messages pretending to come from the platform will follow. In the United States the FTC gave exactly that warning about Canvas.
If the question this leaves you with is which of your records belong in a system of your own, the fit check is a short way to start.
Sources
- Instructure, Security Incident Update & FAQs
- Bloomberg, via Insurance Journal, Some College Finals Delayed After Canvas Online Platform Hacked, 11 May 2026
- Reuters, via Claims Journal, Canvas Parent Reaches Deal With Hackers Behind Recent Breach, 12 May 2026
- Robinson+Cole, via JD Supra, ShinyHunters Hit Instructure + Downs Canvas Learning Management System, 18 May 2026
- National Privacy Commission, NPC Circular 16-03: Personal Data Breach Management, 15 December 2016
Enrique Lacambra III builds internal business systems from Cainta, Rizal.
Tell me what is broken and I will tell you if it is worth building. A 20-minute call, no charge, and I will say so if you do not need me.
