DataBreaches.Net

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

NC: Guilford Technical Community College hit with ransomware

Posted on September 19, 2020 by Dissent

From a statement on Guilford Technical Community College‘s web site that seems to have been removed:

On Sunday, Sept. 13, 2020, GTCC had an unauthorized access to the college network. Campuses were shut down for Monday, Sept. 14, 2020 to limit the extent of the unauthorized access and determine its impact.

As of today’s update to their site, classes will resume in-person on September 21.

GTCC is the second technical college recently hit with ransomware. The first was an attack on Greenville Technical College in South Carolina — an attack whose scope the college initially downplayed. But after the  Avaddon threat actors provided what appeared to be compelling evidence that they had, indeed, exfiltrated personal information, Greenville Tech suddenly went silent publicly. Shortly thereafter, their name and listing disappeared from Avaddon’s leak site, leading many to wonder whether the college had wound up paying ransom after all.  DataBreaches.net has received no response to a September 14 inquiry as to whether they paid ransom or not, but the college has now issued an update.

Now we have Guilford Technical Community College in North Carolina being listed on DoppelPaymer’s leak site.  Were there any operators or worker bees working on both of the attacks on technical colleges?

As noted above and as described in the now-removed notice, archived below, the GTCC attack resulted in the shut down of the campus and disruption of a number of services such as WebAdvisor and Navigate. It also resulted in the closure of a number of college offices.

Notice on GTCC site about the disruption to services due to ransomware attack.

As is typical of the current trend in ransomware attacks, the threat actors do not indicate how much ransom demanded, but do offer some proof of access. In this case, two files were uploaded to the threat actors’ leak site: a document naming the advisors for the college’s clubs, with the advisors’ names and email addresses, and an expense file on COVID-19 related expenses. Neither document contains confidential or sensitive information as both could have been obtained under open records laws or directory information for the campus. But the files make the point that the attackers had access.

This is a developing story and will be updated.

DataBreaches.net also notes that there appeared to be a third technical college whose name appeared briefly on a leak site and then disappeared. It was a technical college that was part of the same South Carolina technical college system as Greenville, but unfortunately, it seems that I did not get any screenshots or record the school’s name or attackers before it disappeared. DataBreaches.net reached out to the South Carolina technical college system to ask how many of their colleges had been attacked or if the whole central system had been attacked.  This post will be updated if a response is received.

This post was edited post-publication to add a link to Greenville’s updated disclosure.


Related:

  • Attorney General James Announces Settlement with Wojeski & Company Accounting Firm
  • JFL Lost Up to $800,000 Weekly After Cyberattack, CEO Says No Patient or Staff Data Was Compromised
  • Before Their Telegram Channel Was Banned Again, ScatteredLAPSUS$Hunters Dropped Files Doxing Government Employees (2)
  • Massachusetts hospitals Heywood, Athol say outage was a cybersecurity incident
  • Data BreachesProsper Data Breach Impacts 17.6 Million Accounts
  • Heritage Provider Network $49.99M Class Action Settlement
Category: Education SectorU.S.

Post navigation

← TX: School district reaches out to FBI following cyberattack
PA: Geisinger Berwick notifying hundreds of patients after firing employee for improper access to records →

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

  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs
  • A jailed hacking kingpin reveals all about the gang that left a trail of destruction
  • Army gynecologist took secret videos of patients during intimate exams, lawsuit says

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

  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[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.