Ransomware Hits Community College of Beaver County During Spring Break — Grades, Transcripts, Financials Encrypted
Attackers timed it perfectly. The first morning of spring break, IT staff at the Community College of Beaver County arrived on campus to find a ransom note waiting for them. Every system was encrypted. Grades locked. Transcripts gone. All financial data inaccessible. Classes scheduled to reopen in one week.
The attack, disclosed March 9, 2026, is the latest in a relentless wave of ransomware targeting American higher education — and it follows a playbook threat actors have refined into a near-perfect formula: hit schools when staff is thin, decision-makers are offline, and the pressure to restore systems fast is highest.
What Happened
Leslie Tennant, CCBC’s vice president of communications, described the discovery Monday morning:
“We came to campus this morning, the first day of spring break, and our IT department notified us that they received a ransom note and that we had been under cyberattack.”
The ransomware encrypted the college’s entire computer network, blocking access to:
- Student grades and academic records
- Transcripts
- All college financial information
- Campus IT infrastructure broadly
The college immediately shut everything down. Staff were told not to use laptops or any campus devices. VPN access from home was cut off. The campus itself was closed as of 9:30 AM Monday.
“We have currently locked down all IT resources. No one is to be using their computers, logging into VPN, even from home,” Tennant said.
The college’s insurance company is now involved, working to identify the attackers and assess whether the encryption can be lifted before any ransom decision is made. CCBC has a one-week window — classes are scheduled to resume next Monday. Without restored systems, they cannot.
The Spring Break Timing Is Not a Coincidence
Ransomware groups do not pick school holidays at random.
Palo Alto Networks’ Unit 42 documented that Vice Society — one of the most active education-sector ransomware groups — deliberately times campaigns to coincide with school calendars, with noticeable spikes during spring and fall months. The reasoning is straightforward:
- Skeleton IT crews: Security and IT staff are on break or reduced schedules
- Slower detection: Fewer eyes on the network means intrusions that began days or weeks earlier go unnoticed longer
- Maximum pressure: A week-long window before mandatory class resumption forces rushed decisions on ransom payment
- Delayed response: Decision-makers are harder to reach, slowing the incident response chain
Jefferson County Schools, Rochester Public Schools, and multiple other institutions have been hit during spring breaks in recent years. CCBC is simply the latest to learn this lesson the hard way.
Higher Education Is the Ransomware Industry’s Favorite Target
The numbers are grim. Education became the most-attacked sector globally in 2025, with schools absorbing an average of 4,388 cyberattacks per week — more than any other industry. Ransomware attacks on educational institutions jumped 23% year-over-year in the first half of 2025 alone.
In the US specifically:
- 251 ransomware attacks hit schools, universities, and colleges in 2025
- The average ransom demand sits around $464,000 (down from $694,000 in 2024, but the average recovery cost ballooned to $4.02 million — nearly four times higher than the year before)
- 3.96 million student and staff records were breached across education sector attacks in 2025
The groups doing the most damage: LockBit, BlackCat/ALPHV, Rhysida, Vice Society, and Clop. All of them have active higher education targeting programs. Rhysida alone hit multiple universities across three continents in 2024-2025. BlackCat claimed North Carolina A&T, Phillips Community College, and Florida International University.
No ransomware group has publicly claimed the CCBC attack yet.
What “Encrypted” Actually Means for Students
The college can’t access grades, transcripts, or financial records. That is not an inconvenience — it is an operational crisis with serious legal implications.
FERPA exposure: Student education records — grades, transcripts, assessment data, financial aid information — are protected under the Family Educational Rights and Privacy Act. When ransomware attackers access and encrypt those records, they have by definition gained unauthorized access to protected student data. If they exfiltrated that data before encrypting it (the standard double-extortion play in 2026), CCBC faces a mandatory breach notification obligation.
The Department of Education can withhold federal funding from institutions that fail to adequately protect student records. For a community college heavily dependent on federal financial aid dollars, that is an existential threat on top of an operational one.
Transcript holds: Students waiting on transcripts for transfer applications, job offers, or graduate school admissions are now in limbo. For community college students — who skew toward working adults with tighter deadlines and less institutional flexibility — this is not a minor disruption.
Financial systems locked: Payroll, vendor payments, financial aid disbursements — all frozen. The longer the systems stay down, the wider the financial damage spreads.
Recovery: One Week Is Optimistic
CCBC has given itself a week to restore operations. Here is what the data says about that timeline.
59% of higher education institutions that suffered ransomware attacks in 2025 recovered within one week. That sounds reassuring until you read the rest of the numbers.
40% of colleges took over a month to recover — double the global average across all sectors. Nine percent reported recovery times of three months or longer. And critically: colleges that paid the ransom were more likely to take longer to recover, not less, with 38% of ransom-payers still struggling after a month versus only 21% of institutions that relied on backups.
The difference between one week and three months often comes down to one thing: whether the college maintained clean, tested, offline backups. If CCBC’s backup infrastructure was connected to the same network that got encrypted — a common failure mode — recovery just got dramatically harder.
The Insurance Question
Behind closed doors Monday, college administration began discussions with its insurance company. This is now standard operating procedure for ransomware incidents, but the conversations are rarely as simple as institutions hope.
Cyber insurance policies covering ransomware have tightened dramatically since 2021. Many now require proof that specific security controls — MFA on all remote access, endpoint detection and response tools, offline backup systems, tested incident response plans — were in place at the time of the attack. If they weren’t, the insurer may dispute coverage.
The insurance company will also weigh in on the ransom payment decision. Some policies cover ransom payments. Others specifically exclude them. Some require law enforcement notification before any payment can be authorized. The FBI strongly discourages ransom payments, noting they fund criminal organizations and do not guarantee data restoration.
Paying does not mean getting your data back. A 2025 survey found that only 54% of organizations that paid a ransom recovered all their data — and the average recovery cost with payment still ran into millions when forensics, remediation, and downtime were factored in.
What CCBC Should Be Doing Right Now
The window for effective response narrows fast. Based on established incident response frameworks, the immediate priorities should be:
In the first 48 hours:
- Preserve all logs and forensic evidence before any remediation begins
- Engage a third-party incident response firm (insurance company will likely mandate this)
- Notify FBI and CISA — FBI’s Recovery Asset Team has resources specifically for education sector attacks
- Assess whether data exfiltration occurred before encryption (changes the legal calculus entirely)
- Identify which backup systems remained uncompromised
This week:
- Determine the full scope of encrypted systems and whether any clean restore points exist
- Brief the Board of Trustees and begin stakeholder communications
- Assess FERPA notification obligations — if student PII was exfiltrated, the clock on breach notification has already started
- Communicate proactively with students about transcript and grade access timelines
Do not:
- Connect any device to the campus network until it has been forensically cleared
- Pay ransom without law enforcement consultation and legal advice
- Assume that paying means data will be restored or not published
A Pattern That Keeps Repeating
Community colleges occupy a uniquely vulnerable position in the ransomware threat landscape. They hold the same categories of sensitive student data as four-year universities — Social Security numbers, financial records, health information, academic records — but typically operate on a fraction of the IT security budget.
The CCBC attack follows the exact same pattern as dozens of others: underfunded IT department, networked backup systems, holiday-timed strike, ransom note discovered by skeleton crew. The attackers did not need sophisticated tools or nation-state capabilities. They needed access and time — and most likely got both weeks before anyone noticed.
The question CCBC needs to answer — and every community college in America should be asking right now — is not just how to recover from this attack. It’s whether the security investments being made are proportionate to the value and sensitivity of the data being held, and the certainty that attackers are coming.
The next spring break is not that far away.
Follow Breached Company for updates as this story develops.



