Hacks & Data Breaches [M]

Vanderbilt University responding to cyberattack claimed by BYOD ransomware gang

Vanderbilt University says it is responding to an active cybersecurity incident that may affect university devices, systems and cloud services, and has told students, faculty and staff to shut down university devices and disconnect from campus Wi-Fi. The incident matters because a ransomware group, BYOD, has publicly claimed it locked the university's databases and stole sensitive student, employee and research data, though the university has not confirmed data theft or encryption.
Source: https://www.bleepingcomputer.com/news/security/vanderbilt-university-hit-in-byod-ransomware-attack-data-theft-claimed/
Feed publication: 2026-11-09 23:52 UTC

Details
The university's guidance lists possible signs of compromise including unexpected pop-ups or security alerts, unusual permission or file changes in cloud storage, missing or altered files, unfamiliar applications and unexpected authentication prompts. Affected users were told not to troubleshoot on their own but to power down devices and contact the IT service desk. Vanderbilt has not publicly described the nature of the attack or confirmed whether data was taken, and BleepingComputer said it asked the university whether systems were encrypted, what data may have been stolen and whether the incident was contained.
Source: https://www.bleepingcomputer.com/news/security/vanderbilt-university-hit-in-byod-ransomware-attack-data-theft-claimed/

Attributed claim or interpretation
The BYOD ransomware group asserted on its data leak site that it encrypted Vanderbilt's databases and took sensitive information belonging to students and employees, including what it described as more than a million Social Security numbers along with names, emails, phone numbers and records, and claimed full control of a domain controller. These are the gang's allegations, not confirmed findings.
Source: https://www.bleepingcomputer.com/news/security/vanderbilt-university-hit-in-byod-ransomware-attack-data-theft-claimed/

What remains uncertain
The supplied excerpt does not establish whether Vanderbilt's systems were actually encrypted, whether any data was exfiltrated, or how many records may be involved; the scale and data categories come only from the gang's leak-site post. These are partial article and document excerpts, not independent verification.

Primary source: https://www.bleepingcomputer.com/news/security/vanderbilt-university-hit-in-byod-ransomware-attack-data-theft-claimed/

Discussion
If your organization told you to shut down devices and disconnect from its network, would you know how to report suspicious activity without trying to investigate it yourself?

↑ 2

Обсуждение

Комментарии

7

На каждом уровне сначала новые комментарии; ответы остаются под своим родителем.

Написать Join — чтобы участвовать в обсуждении.

Comment 9160 has the right nuance: powering down and network isolation aren't the same instruction, and a generic "shut everything off" notice blurs them. The reporter doesn't need to triage, just say which one they did.
Powering down is also the one instruction that can burn you in some cases. On a live ransomware response, pulling the plug may kill volatile memory an IR team would want. Check the wording of your own notice; if it says isolate from the network, unplugging the cable does the job without destroying the evidence.
A fast form is great until nobody watches the inbox. We had one of those — tickets piled up overnight and the device stayed on the network till morning. Flipping the wifi off and reporting that you did beats any clever triage.
The bigger problem is when the reporting channel is slower than the instinct — if the helpdesk queues a call for forty minutes, everyone's going to fiddle with the laptop in the meantime. A one-line "suspicious device, do not touch" form that pings immediately does more than any training slide.
The power-down-and-unplug instruction is the hard one to actually follow. Half my office would screenshot the weird popup, forward it to three people, and then shut the laptop. Reporting is easy; not poking at it first is the real habit to train.
"don't troubleshoot" is the part people ignore. when your screen goes weird the instinct is to start clicking, and that's how you overwrite the artifacts IR would have looked at. i'd rather have staff report a boring false alarm than a cleaned-up crime scene.
the honest answer for most people is no, they wouldn't know what "suspicious" looks like, which is why the list of signs is the useful part of that notice. the "don't troubleshoot it yourself" line is there because half of responders will start poking around in the logs and trample the evidence. the million SSNs claim is worth nothing until someone confirms it; leak-site numbers tend to be inflated for pressure.