ShinyHunters breach Instructure Canvas LMS, claim 275M users and 3.65TB of student data from 9,000 schools including 44 Dutch institutions



TL;DR

ShinyHunters breached Instructure’s Canvas learning management system, claiming 3.65 terabytes of data from 275 million users across 9,000 institutions worldwide, including private messages between students and teachers. Forty-four Dutch universities and schools are confirmed affected, and the breach, the second at Instructure in eight months, exposes the structural risk of vendor concentration in education technology.

 

The largest education data breach in history was not an attack on a school. It was an attack on a vendor. On 30 April, hackers exploited a vulnerability in the systems of Instructure, the company that makes Canvas, the learning management system used by 41 per cent of higher education institutions across North America.

The criminal group ShinyHunters, which previously orchestrated the Snowflake supply chain attacks that compromised Ticketmaster and AT&T, claims to have stolen 3.65 terabytes of data affecting 275 million users across nearly 9,000 educational institutions worldwide, including private messages between students, teachers, and staff.

In the Netherlands, 44 universities and schools are confirmed affected, from the University of Amsterdam and Vrije Universiteit to The Hague University of Applied Sciences. Dutch authorities have told students and staff to be vigilant. The hackers have told Instructure to pay up by 8 May or the data goes public.

And the breach exposes a structural vulnerability in the way education has been digitised: the schools did not choose to be attacked, and they could not have prevented it, because the decision to entrust student data to a single vendor was made years ago, and the vendor’s security was never theirs to control.

The company

Instructure was founded in 2008 and built Canvas into the dominant learning management platform in the United States, overtaking Blackboard to claim 31 per cent of the North American higher education LMS market by 2018. The company went public in 2015, was taken private by Thoma Bravo in a two billion dollar deal in 2020, and was sold again to KKR and Dragoneer Investment Group in November 2024 for 4.8 billion dollars.

 

The company now operates as a private entity owned by one of the world’s largest alternative asset managers, serving approximately 200 million learners across more than 100 countries. Its products include Canvas LMS, Canvas Studio for video-based learning, and Mastery Assessment for competency tracking. The platform is embedded in the daily academic life of students from secondary school to postgraduate programmes, handling course materials, assignment submissions, grades, and, critically, direct messages between students and educators.

 

This is Instructure’s second confirmed breach in approximately eight months. In September 2025, ShinyHunters exploited a social engineering attack against the company’s Salesforce environment. The April 2026 attack exploited a vulnerability in Instructure’s production systems, which the company says has since been patched. Instructure’s chief information security officer Steve Proud notified customers on 1 May that the company had experienced a cybersecurity incident, confirming that the exposed data may include names, email addresses, student identification numbers, and Canvas Inbox and Discussion messages.

 

The company says there is no indication that dates of birth, government identifiers, financial information, or passwords were compromised. But the inclusion of private messages, which could contain phone numbers, home addresses, and personal information shared in the expectation of privacy, makes the breach qualitatively different from a typical email-and-name data leak.

The attackers

ShinyHunters is a criminal hacking and extortion group that has been active since 2020 and has become one of the most prolific data thieves in the world. The group, believed to comprise a small number of core members based in Canada and France, specialises in targeting companies that provide services to multiple organisations, allowing a single breach to cascade across thousands of victims.

 

In 2024, ShinyHunters orchestrated the Snowflake supply chain campaign, compromising approximately 165 organisations including Ticketmaster, where 560 million records were exposed, and AT&T, where data on 110 million customers was stolen. AT&T paid a 370,000 dollar ransom to have the data deleted. In March 2026, ShinyHunters breached the European Commission, leaking 350 gigabytes of data from 42 internal clients and at least 29 EU entities. The group’s method is consistent: identify a vendor or platform with access to large volumes of data, exploit a vulnerability or social engineering vector, exfiltrate the data, and demand payment under threat of public release.

 

The Instructure breach follows this pattern precisely. ShinyHunters posted its claim on a dark web forum on 2 May, listing 8,809 school districts, universities, and online education platforms with per-institution record counts. The group warned Instructure to “make the right decision” before 6 May, later extended to 8 May, or face the release of the full dataset along with what it described as “several annoying digital problems.” The hackers claim to possess billions of private messages.

 

The cybersecurity industry has been predicting that 2026 would be the year of governed security AI, with automated threat detection and response systems reaching operational maturity. Instructure’s breach suggests the governance gap between enterprise security posture and attacker capability remains wide, and that the organisations most vulnerable are not the ones with the weakest security but the ones whose vendors have the widest blast radius.

The vulnerability

The structural problem the breach exposes is vendor concentration. Canvas dominates its market because it is good: the platform is well-designed, reliable, and deeply integrated into institutional workflows. But dominance means that a single security failure at a single company can compromise the academic records and private communications of students across 9,000 institutions in dozens of countries simultaneously. The schools and universities affected by the breach had no role in the security decisions that allowed it. They were not consulted about the vulnerability that was exploited.

 

They cannot independently audit the security of the systems that hold their students’ data. They are, in the language of cybersecurity, downstream. Europe has been dismantling and rewriting its own regulatory rulebook in an attempt to balance innovation and security, but the Canvas breach demonstrates that the education sector sits in a regulatory gap: schools are subject to data protection obligations under GDPR and, in the Netherlands, the new Cybersecurity Act transposing NIS2, yet their ability to meet those obligations depends on the security practices of a private company owned by a private equity firm on another continent.

 

The EU’s ongoing struggles to finalise its AI Act amendments illustrate the broader challenge: regulation consistently lags behind the speed at which technology concentrates data and the speed at which attackers exploit that concentration. NIS2 imposes breach reporting requirements and fines of up to 10 million euros or two per cent of global turnover for non-compliance, and the Cyber Resilience Act, which begins to apply in September 2026, will mandate vulnerability reporting for products with digital elements.

But the education sector’s reliance on a small number of dominant platforms means that compliance at the institutional level cannot prevent a breach at the vendor level. The 44 Dutch institutions affected by the Canvas breach may have been fully compliant with every applicable regulation and still had no capacity to prevent or mitigate the attack.

The pattern

The Instructure breach is the latest in a series of attacks on education technology vendors that collectively demonstrate the sector’s status as one of the softest targets in the global economy. In December 2024, PowerSchool, which provides administrative software to K-12 schools, was breached, and the attacker demanded 2.85 million dollars in ransom, which the company paid.

 

Education technology platforms have become some of the most widely used consumer applications in the world, with companies like Duolingo reporting 56.5 million daily active users, yet the industry’s security maturity has not kept pace with its user growth. The edtech sector collects sensitive data on minors, stores private academic communications, and operates with a user base that has limited capacity to protect itself. The combination of high data value, low security investment relative to other sectors, and a user base that includes children makes education technology an attractive target for criminal groups.

 

The question of whether European digital regulation can deliver both innovation and security is not abstract for the 44 Dutch institutions now advising students to change passwords and monitor their accounts. The private equity ownership model that has shaped Instructure’s trajectory, from Thoma Bravo’s two billion dollar take-private to KKR’s 4.8 billion dollar acquisition, optimises for revenue growth, cost efficiency, and eventual exit. Whether it optimises for security investment is a question that the breach has answered. Instructure’s Canvas is a product that 200 million learners depend on daily.

 

The company that owns it was breached twice in eight months by the same criminal group. The schools had no say in the vendor’s security architecture, no visibility into its vulnerability management, and no ability to prevent the compromise of their students’ data. The students have been told to be vigilant. Vigilance, in this context, means accepting that the data is gone and hoping it is not weaponised. The vendor model that digitised education at scale also concentrated the risk at scale, and the breach is the cost.



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


Vibe coding has taken the development world by storm—and it truly is a modern marvel to behold. The problem is, the vibe coding rush is going to leave a lot of apps broken in its wake once people move on to the next craze. At the end of the day, many of us are going to be left with apps that are broken with no fixes in sight.

A lot of vibe “coders” are really just prompt typers

And they’ve never touched a line of code

An AI robot using a computer with a prompt field on the screen. Credit: Lucas Gouveia / How-To Geek

Vibe coding made development available to the masses like never before. You can simply take an AI tool, type a prompt into a text box, and out pops an app. It probably needs some refinement, but, typically, version one is still functional whenever you’re vibe coding.

The problem comes from “developers” who have never written a line of code. They’re just using vibe coding because it’s cool or they think they can make a quick buck, but they really have no knowledge of development—or any desire to learn proper development.

Think of those types of vibe coders as people who realize they can use a calculator and online tools to solve math problems for them, so they try to build a rocket. They might be able to make something work in some way, but they’ll never reach the moon, even though they think they can.

Anyone can vibe code a prototype

But you really need to know what you’re doing to build for the long haul

For those who don’t know what they’re doing, vibe coding is a fantastic way to build a prototype. I’ve vibe coded several projects so far, and out of everything I’ve done, I’ve realized one thing—vibe coding is only as good as the person behind the keyboard. I have spent more time debugging the fruits of my vibe coding than I have actually vibe coding.

Each project that I’ve built with vibe coding could have easily been “viable” within an hour or two, sometimes even less time than that. But, to make something of actual quality, it has always taken many, many hours.

Vibe coding is definitely faster than traditional coding if you’re a one-man team, but it’s not something that is fast by any means if you’re after a quality product. The same goes for continued updates.

I’ve spent the better part of three months building a weather app for iPhone. It’s a simple app, but it also has quite a lot of complex things going on in the background.

It recently got released in the App Store—no small feat at all. But, I still get a few crash reports a week, and I’m constantly squashing bugs and working on new features for the app. This is because I’m planning on supporting the app for a long time, not just the weekend I released it, and that takes a lot more work.

Vibe coders often jump from app to app without thinking of longevity

The app was a weekend project, after all

A relaxed man lounging on an orange beanbag watches as a friendly yellow robot works on a laptop for him, while multiple red exclamation-mark warning icons float around them. Credit: Lucas Gouveia/How-To Geek | ViDI Studio/Shutterstock

I’ve seen it far too often, a vibe coder touting that they built this “complex app” in 48 hours, as if that is something to be celebrated. Sure, it’s cool that a working version of an app was up and running in two days, but how well does it work? How many bugs are still in it? Are there race conditions that cause a random crash?

My weather app has a weird race condition right now I’m tracking down. It crashes, on occasion, when opened from Spotlight on an iPhone. Not every time does that cause a crash, just sometimes.

If a vibe coder’s only goal is to build apps in short amounts of time so they can brag about how fast they built the app, they likely aren’t going to take the time to fix little things like that.

I don’t vibe code my apps that way, and I know many other vibe coders that aren’t that way—but we all started with actual coding, not typing a prompt.


Anyone can be a vibe coder, but not all vibe coders are developers

“And when everyone’s super… no one will be.” – Syndrome, The Incredibles. It might be from a kids’ movie, but it rings true in the era of vibe coding. When everyone thinks they can build an app in a weekend, everyone thinks they’re a developer.

By contrast, not every vibe coder is actually a developer, and that’s the problem. It’s hard to know if the app you’re using was built by someone who has plans to support the app long-term or not—and that’s why there’s going to be a lot of broken apps in the future.

I can see it now, the apps that people built in a weekend as a challenge will simply go without updates. While the app might work for the first few weeks or months just fine, an API update comes along and breaks the app’s compatibility. It’s at that point we’ll see who was vibe coding to build an app versus who was vibe coding just for online clout—and the sad part is, consumers will lose out more often than not with broken apps.



Source link