Menu
Browse

Cyber Threat Actor: Ryuk

Actor Type Location Known Incidents
 Icon
Criminal
United States of America
1 incident
Profile

Ryuk Ransomware is the alias used for a ransomware operation that has been publicly linked to activity originating from the United States of America. The actor is known primarily for deploying the Ryuk ransomware family against targets, with one documented incident involving a county government in April 2019. In that case the attack disrupted the county’s website and internal systems, forcing employees to rely on external communication tools such as Gmail and social media while essential services like online payment processing, social services operations, and real estate transaction handling were compromised. The disruption delayed home purchases and fund transfers, leading to public frustration over the prolonged outage affecting critical functions. Officials confirmed the ransomware intrusion, refused to meet the bitcoin ransom demand, and engaged a private security firm to restore operations while maintaining minimal essential services. The incident illustrates the actor’s focus on financial gain through extortion and its capacity to cause significant operational disruption within the public sector.

The ransomware’s typical initial access vector, as indicated in the reported case, involves malicious links or attachments, a common phishing‑style technique that mirrors patterns observed in other Ryuk incidents. No explicit public attribution to a state sponsor or criminal consortium is provided in the available sources, so any affiliation remains unspecified based on the given information. The April 2019 county government attack serves as a representative example of the actor’s methodology, demonstrating how Ryuk ransomware can be used to encrypt critical data, demand payment in cryptocurrency, and impose substantial service interruptions on targeted organizations. This profile reflects only the facts presented in the source material and avoids speculation beyond those details.

Incidents
Attributed incidents available to members
1 incident
Sources
Sources available to members
0 sources