Incident Score: Analysis & Impact (HUN1782426290)
The details regarding individual company incidents & reports gives you full view from every side.
Rankiteo Score Impact Analysis
Key Highlights From The Incident Analysis
- Timeline of Huntress's Ransomware and lateral movement inside company's environment.
- Overview of affected data sets, including SSNs and PHI, and why they materially increase incident severity.
- How Rankiteo’s incident engine converts technical details into a normalized incident score.
- How this cyber incident impacts Huntress Rankiteo cyber scoring and cyber rating.
- Rankiteo’s MITRE ATT&CK correlation analysis for this incident, with associated confidence level.
Full Incident Analysis Transcript
In this Rankiteo incident briefing, we review the Huntress breach identified under incident ID HUN1782426290.
The analysis begins with a detailed overview of Huntress's information like the linkedin page: https://www.linkedin.com/company/huntress-labs, the number of followers: 120630, the industry type: Computer and Network Security and the number of employees: 847 employees
After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 728 and after the incident was 618 with a difference of -110 which is could be a good indicator of the severity and impact of the incident.
In the next step of the video, we will analyze in more details the incident and the impact it had on Huntress and their customers.
Huntress recently reported "Huntress Faces Allegations of Insider Threat Linked to Ransomware Group", a noteworthy cybersecurity incident.
Security firm Huntress is embroiled in controversy after a former employee, Ben Folland, accused the company of concealing an insider threat involving a current employee allegedly leaking information to a ransomware operation.
The disruption is felt across the environment, and exposing Law enforcement communications, Internal memos, Recorded conversations.
In response, and stakeholders are being briefed through Limited public disclosure due to legal constraints.
The case underscores how Ongoing, with advisories going out to stakeholders covering CEO Kyle Hanslovan acknowledged concerns but disputed insider threat claims.
Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.
The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.
MITRE ATT&CK® Correlation Analysis
Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Trusted Relationship (T1199) with high confidence (90%), supported by evidence indicating current employee allegedly leaking information to a ransomware operation. Under the Credential Access tactic, the analysis identified Unsecured Credentials: Credentials In Files (T1552.001) with moderate to high confidence (70%), supported by evidence indicating law enforcement communications, Internal memos compromised. Under the Collection tactic, the analysis identified Data from Local System (T1005) with moderate to high confidence (80%), supported by evidence indicating internal memos, Recorded conversations between employee and DevMan and Automated Collection (T1119) with moderate confidence (60%), supported by evidence indicating allegedly shared communications from U.S. law enforcement. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (80%), supported by evidence indicating employee had shared communications with a cybercriminal known as *DevMan*. Under the Impact tactic, the analysis identified Data Destruction (T1485) with lower confidence (40%), supported by evidence indicating ransomware operator targeting Folland and his family and Defacement: Internal Defacement (T1491.001) with moderate confidence (50%), supported by evidence indicating reputational damage, Legal threats against whistleblower. Under the Defense Evasion tactic, the analysis identified Impair Defenses: Disable or Modify Tools (T1562.001) with moderate confidence (60%), supported by evidence indicating huntress attempted to silence him with legal threats and Disabling Security Tools (T1089) with moderate confidence (50%), supported by evidence indicating limited public disclosure due to legal constraints. Under the Command and Control tactic, the analysis identified Application Layer Protocol: Web Protocols (T1071.001) with moderate to high confidence (70%), supported by evidence indicating cybercriminal known as *DevMan*, a ransomware operator. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Huntress Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/huntress-labs/incident/HUN1782426290
- Huntress CyberSecurity Rating page: https://www.rankiteo.com/company/huntress-labs
- Huntress Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/hun1782426290-huntress-ransomware-december-2025/
- Huntress CyberSecurity Score History: https://www.rankiteo.com/company/huntress-labs/history
- Huntress CyberSecurity Incident Source: https://www.theregister.com/cyber-crime/2026/06/25/ex-huntress-analyst-claims-company-insider-fed-info-to-a-ransomware-crim-social-media-drama-ensues/5262538
- Rankiteo A.I CyberSecurity Rating methodology: https://www.rankiteo.com/Images/rankiteo_algo.pdf
- Rankiteo TPRM Scoring methodology: https://static.rankiteo.com/model/rankiteo_tprm_methodology.pdf