Rowan Grey (@FifthThread) header
Rowan Grey (@FifthThread) profile picture

Independent Journalist specializing in Cybercrime Interviews and News.

Joined March 2012
Photo by Rowan Grey (@FifthThread)Photo by Rowan Grey (@FifthThread)Photo by Rowan Grey (@FifthThread)Photo by Rowan Grey (@FifthThread)Photo by Rowan Grey (@FifthThread)Photo by Rowan Grey (@FifthThread)Photo by Rowan Grey (@FifthThread)Photo by Rowan Grey (@FifthThread)Photo by Rowan Grey (@FifthThread)Photo by Rowan Grey (@FifthThread)
Mouse in the middle attack lol 😆 Monday humor 🤣. Have a good week everyone. #itsupportspecialist #desktopsupport #desktopsupporttechnician #desktopengineer #helpdesk #helpdesktechnician #servicedesk
2
2
5
616
Truth!
my AI agents after I give them full access and tell them to be careful
29
Interested in hearing from anyone who's investigated this further.
🇷🇺 🚨 RUSSIA: BORDER CROSSING DATABASE WITH 1M+ RECORDS ALLEGEDLY OFFERED FOR SALE A threat actor on a dark web forum is advertising a database of more than 1 million records of border crossings into Russia, allegedly from Russian border control systems. According to the post: • The data reportedly covers crossings in 2021 and 2022, for Russian citizens and foreign nationals • Fields allegedly include full names, document numbers, issue dates and country of issue • Checkpoint locations, type of operation, transport and flight details are also claimed • The set is split into three archives and priced in crypto; samples were shared as proof ⚠️ Analyst Note: Unverified threat-actor claim, NOT confirmation of a breach. The records are from 2021 to 2022, so this may be older data rather than a fresh compromise. If genuine, travel histories tied to passport numbers carry real surveillance, profiling and fraud risk. Russian authorities have not commented. #DDW #DarkWeb #Russia #DataBreach #BorderSecurity #Government #ThreatIntelligence
18
Emerging Threat Actor: Syntax I am documenting the group's publicly presented identifiers for tracking and research purposes.
27
I reached out directly to BYOD regarding the attack on UNM and received a response. I've shared in the thread below. @UNM, I'd welcome your perspective on these claims, particularly regarding the impact on UNM Hospital and the reported disruption to patient care 🧵👇
3
1
3
1,513
BYOD argues that a README file left on affected devices supports its claim that the attack was intended to target the university, not hospital operations. The group says the file repeatedly referenced the university and described the data being locked as informational.
1
1
47
I appreciate BYOD taking the time to share its perspective and provide additional context about the incident. Their response offers further insight into their account of what happened, and I hope continued dialogue will help bring greater clarity to the situation.
1
45
6
78
4
643
14,389
BYOD claims most of the data it accessed consisted of small, compressed files associated with old, inactive accounts labeled scim__users_{numerical_identifier}. The group says it interpreted these as forgotten university devices and user data. That interpretation is BYOD's.
1
12
BYOD also argues that a README file left on affected devices supports its claim that the attack was intended to target the university, not hospital operations. The group says the file repeatedly referenced the university and described the data being locked as informational.
1
17
Important distinction: this is BYOD's personal accounting of the details.
13
BYOD claims its original target was the University of New Mexico, not UNM Hospital (UNMH). The group says both entities shared a network and group policy, which allegedly contributed to hospital-related data being caught up in the attack.
1
48
🚨 BREAKING: I reached out directly to BYOD, the threat actor group behind the UNM cyberattack. They responded with several messages disputing aspects of the incident's reporting and explaining why they claim UNM Hospital was affected. Here’s what they told me. 🧵
1
1
2
76
BYOD reportedly offered free decryption for UNM's hospital systems and up to $2,500 per affected patient, while claiming it hadn't realized patient care was involved. Those statements have now been removed. I've reached out to BYOD for comment. I'll update if they respond.
1
34