320,000 school files on the dark web: the Bristol breach shows how one shared platform can expose many schools at once

More than 320,000 files stolen from Bristol City Council's Trading with Schools platform have been published by criminals on the dark web. The platform serves 88 schools, and the council says personal data was taken from 39 of them. Months after the attack, the council still cannot confirm exactly which schools, pupils or staff are affected. The case is a lesson in how shared education systems concentrate risk.

5 min read

320,000 school files on the dark web: the Bristol breach shows how one shared platform can expose many schools at once

Trading with Schools is an IT platform that Bristol City Council provides to schools in its area. Schools use it for day-to-day work: timetabling, lesson plans, staff records and payroll. Some of its content is sensitive. The council has said the platform can hold information about children, including educational psychology files.

Date

Event

21 September 2026

Malicious software infiltrates the platform, according to the BBC and Computing.co.uk

25 September 2026

The council becomes aware of the attack four days later and shuts the platform down

27 October 2026

The group behind the attack adds Bristol City Council to its data leak site, reportedly with little supporting evidence and no ransom demand

4 November 2026

The council confirms that more than 320,000 files have been published on the dark web

The council says personal data was taken from 39 schools. Of the 88 schools using the platform, 49 buy only internet services from the council. The remaining 39 rely far more heavily on the platform, which is why their data was held there.

Why the scope is still unclear

The council has said it is still reviewing the published material to establish what kind of information it contains, which schools are affected and which individuals may be at risk. It has said it cannot confirm the precise details at this stage.

That gap is important. A figure of 320,000 files describes the volume of material, not the number of people affected. Files can contain duplicates, drafts or records about many different people. Until the council completes its review, families cannot know whether a particular child or member of staff is included.

The council has also said that disruption to school life has been real. Many schools have been unable to use their telephone systems, and the authority is working with them to provide advice on protecting personal information.

What the data may contain

The council has not published a list of the stolen data. Based on what the platform is used for, the material could include:

  • timetables, lesson plans and scheduling records

  • staff details and payroll information

  • educational psychology files relating to pupils

The last category is the most sensitive. Records of this kind can describe a child's learning needs, behaviour or family circumstances. Information like this can be used for targeted scams, impersonation or pressure tactics against families, which is why the council has asked parents to remain alert.

Why shared platforms are attractive targets

The Bristol case illustrates concentration risk. When one platform serves dozens of schools, one successful intrusion can expose data from all of them at once. The attacker needs to find one weakness, while each school would need to defend the same platform separately. That makes a shared system both efficient for the council and an attractive target for criminals.

The response timeline also matters. The council discovered the attack four days after it happened and shut the platform down only then. Comparitech, a data research company, has criticised that delay, noting that it gave attackers time to move through the system and take data. Whether the response could have been faster is a question the council will need to answer as its investigation continues.

Publication on a leak site is a common final step in these attacks. Criminal groups often post files there when a victim refuses to pay. In Bristol, no ransom demand has been reported.

What schools, families and IT teams should do

For families. Contact your child's school to ask whether they have been notified. Be cautious about unexpected messages that mention your child's school, the council or the breach, as scammers often exploit news like this. Use strong, unique passwords for important accounts. The UK's National Cyber Security Centre publishes guidance on what to do after a data breach.

For schools. Find out which systems hold personal data and whether any copy remains on third-party platforms. Review which records you need to keep and for how long. Make sure that staff know how to report suspicious activity quickly, because a delay of several days can make an intrusion far more damaging.

For councils and other providers of shared platforms. Limit what any single platform holds, enforce multi-factor authentication for administrative access, and rehearse shutdown and isolation procedures. Plans should cover how to notify schools and families quickly, even before the scope of the breach is known.

The lesson

Most of the damage in the Bristol case comes from two things: the sensitivity of the data and the reach of a single platform. Neither is unusual, which is why this incident matters beyond Bristol. Education providers across the UK and elsewhere run shared systems that hold similar records.

The most useful question for any school or council is not only "could this happen to us?" It is also "if it did, how many people would we be able to identify within days, and how quickly could we tell them?" In Bristol, the answer is still not clear months after the attack, and that uncertainty is itself a cost for the families affected.