DataBreaches.Net

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

Guilford Technical Community College notifies 65,646 affected by ransomware incident in 2020

Posted on January 14, 2022 by Dissent

On September 19, 2020, DataBreaches.net reported that Guilford Technical Community College (GTCC) in North Carolina had reportedly become a ransomware victim of DoppelPaymer on September 13.

The following month, this site followed up by asking whether GTCC had notified the more than 43,000 students whose data had appeared on the dark web. A spokesperson for the college responded:

Guilford Technical Community College has notified faculty, staff and students of a recent ransomware cyberattack. This communication was in response to an unauthorized access to the college’s network, which was discovered on Sept. 13, 2020.

Upon discovery of the event, the College immediately launched an investigation, with the assistance of leading cybersecurity experts, the Federal Bureau of Investigation, and other state agencies to determine what happened and to remediate impacted systems.

Additionally out of an abundance of caution, the college is proactively taking the necessary steps to assist those individuals who have been potentially impacted by the attack. The college’s faculty, staff and students will be offered free credit monitoring and identity restoration services.

So in October, 2020, the college said those potentially impacted would be offered credit monitoring and identity restoration services. But it seems that those offers may not have been made until this week.

Yesterday, external counsel for GTCC notified the Maine Attorney General’s Office about the breach. Their notification indicated that a total of 65,646 current or former students, faculty members, or staff members were being notified of the incident and that written notification would go out on January 13, 2022. A sample notification letter for adults was attached to the submission.

One of the most shocking aspects of the notification (apart from its delay) is that it does not mention that data was leaked on the dark web back in October 2020.

From part of the sample notification letter (emphasis added by this site):

You are receiving this letter as the data mining determined that your personal information was present on GTCC’s network at the time of the attack and may have been accessible to the cybercriminal as a result. This personal information includes your: name, <>. There is no confirmation that this personal information was accessed or acquired by the cybercriminal(s).

“May have been accessible?” “No confirmation that this personal information was accessed or acquired?” Seriously?  Is that what they wrote to all the people whose personal information was actually leaked on the dark web?

Perhaps there is another letter that went to people who had their personal information leaked on the dark web?

DataBreaches.net sent an email inquiry to GTCC to ask whether there was an alternative notification for those who had their data leaked in October 2020. No reply has been received.

So almost 1.5 years after a ransomware incident, those impacted are sent a letter that may be misleading at best, with an offer for help that they should have been made back in October, 2020.

Does the government thinks that is just fine? As this site pointed out in 2020, the Federal Trade Commission can enforce data security for financial aid data under the GLBA. Why don’t they? And what is the U.S. Education Department doing?

 

 

Category: Breach IncidentsCommentaries and AnalysesEducation SectorMalwareU.S.

Post navigation

← Former Acting Inspector General for the U.S. Department of Homeland Security Pleads Guilty to Scheme to Defraud the U.S. Government
The definitions of “recently” and “discovered” leave a lot to be desired →

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

  • Nova Scotia Power hit by cyberattack, critical infrastructure targeted, no outages reported
  • Georgia hospital defeats data-tracking lawsuit
  • 60K BTC Wallets Tied to LockBit Ransomware Gang Leaked
  • UK: Legal Aid Agency hit by cyber security incident
  • Public notice for individuals affected by an information security breach in the Social Services, Health Care and Rescue Services Division of Helsinki
  • PowerSchool paid a hacker’s extortion demand, but now school district clients are being extorted anyway (3)
  • Defending Against UNC3944: Cybercrime Hardening Guidance from the Frontlines
  • Call for Public Input: Essential Cybersecurity Protections for K-12 Schools (2025-26 SY)
  • Cyberattack puts healthcare on hold for hundreds in St. Louis metro
  • Europol: DDoS-for-hire empire brought down: Poland arrests 4 administrators, US seizes 9 domains

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

  • Apple Siri Eavesdropping Payout Deadline Confirmed—How To Make A Claim
  • Privacy matters to Canadians – Privacy Commissioner of Canada marks Privacy Awareness Week with release of latest survey results
  • Missouri Clinic Must Give State AG Minor Trans Care Information
  • Georgia hospital defeats data-tracking lawsuit
  • No Postal Service Data Sharing to Deport Immigrants
  • DOGE aims to pool federal data, putting personal information at risk
  • Privacy concerns swirl around HHS plan to build Medicare, Medicaid database on autism

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.
Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report