DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

Mum’s the word? What are these school districts doing after a recent breach?

Posted on December 9, 2020 by Dissent

On November 15, ABC in Chicago reported that suburban school district Township High School District 211 experienced a security breach in which outgoing emails, phone calls, and text messages had been compromised over the weekend.  Parents reported receiving offensive messages, some of which were sexual.

On November 20, Patch reported that a teacher’s account in Niles Township High School District 219 had been hijacked the previous week and misused to send offensive emails to students and community members.

District 211?  District 219? Were these reports connected? It appears that they were and that it wasn’t just these two districts. The Chicago Tribune reported that  incidents occurred on the night of Nov. 11 in both Maine Township High School District 207 and Niles Township High School District 219. School districts’ web sites were also altered to display offensive messages, and law enforcement was investigating reports from all three districts.

And then…. silence.  Law enforcement said no more and the districts did not reveal more about the incidents in terms of the security issues — they focused on denouncing the inappropriate, racist, and lewd material.

Denouncing hate speech is certainly appropriate, but how did this breach happen? And what will prevent if from happening again?

Why have the districts remained silent?


If you are a parent of a student in District 207, 211, 213, or 219 and have information about this incident, please contact databreaches.net.


DataBreaches.net was recently contacted by an individual who provided this site with additional information on the incident.  According to this source, who asked to remain anonymous but who states that they were involved in the investigation, the incident involved three students at Niles who executed a credential stuffing attack — and not just on Districts 207, 211, and 219, but on a dozen or more districts in Illinois, Ohio, Wisconsin, and potentially other states.

The credential stuffing attack gave the students login credentials to multiple student and staff accounts, which they then misused to send vulgar emails and to create new accounts for themselves on the systems they accessed.

“The common theme here,” the source explained, “is the districts were using one authentication provider (mostly Google for schools) which allowed access to many other systems the students and staff use.  A single compromised staff administrator level account granted access to multiple applications and opportunities to do bad things.”

The investigators did uncover the identity of the students involved in the incident, but what the districts have done in response in terms of filing charges is not known to DataBreaches.net at this point. Nor does this site know what disciplinary action the district has taken.

DataBreaches.net sent multiple inquiries about this incident to Districts 207, 211, and 219, and one inquiry to District 213.  There have been no responses at all, begging the question:

What is going to prevent this from happening again and again?  What have the districts done in response to prevent a recurrence?

Yes, we need to hold the kids accountable, but we also need to hold school districts accountable for weak security.  Who’s holding them accountable and insisting they up their game?

 



			
Category: Breach IncidentsEducation SectorHackInsiderU.S.

Post navigation

← TX: Fraudsters who stole health information to fund spending spree plead guilty
In Battle Against Hackers, Companies Try to Deceive the Deceivers →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • CoinMarketCap Hacked, Scrambles to Remove Malicious Wallet Verification Popup
  • Montana Attorney General launches investigation into Lee Enterprises data breach
  • AT&T gets preliminary approval for $177 million data breach settlement
  • Aflac notifies SEC of breach suspected to be work of Scattered Spider
  • Former JBLM soldier pleads guilty to attempting to share military secrets with China
  • No, the 16 billion credentials leak is not a new data breach — a wake-up call about fake news (Updated)
  • Tonga’s health system hit by cyberattack (1)
  • Russia Expert Falls Prey to Elite Hackers Disguised as US Officials
  • Proposed class action settlement in In re Netgain Technology litigation
  • Qilin Offers “Call a lawyer” Button For Affiliates Attempting To Extort Ransoms From Victims Who Won’t Pay

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • The Markup caught 4 more states sharing personal health data with Big Tech
  • Privacy in the Big Sky State: Montana’s Consumer Privacy Law Gets Amended
  • UK Passes Data Use and Access Regulation Bill
  • Officials defend Liberal bill that would force hospitals, banks, hotels to hand over data
  • US Judge Invalidates Biden Rule Protecting Privacy for Abortions
  • DOJ’s Data Security Program: Key Compliance Considerations for Impacted Entities
  • 23andMe fined £2.31 million for failing to protect UK users’ genetic data

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net

Mastodon: Infosec.Exchange/@PogoWasRight

Signal: +1 516-776-7756

DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.