UK Ties GRU to Microsoft 365 Credential-Stealing Malware
UK Sanctions Russian Intelligence Units for Sophisticated cyber Operations, Including “AUTHENTIC ANTICS” Malware
the UK government has taken decisive action, imposing sanctions on three Russian GRU (Main Intelligence Directorate) units and 18 Russian individuals for thier involvement in a range of malicious cyber activities. This move, announced by the National Cyber Security Center (NCSC), directly attributes the deployment of a sophisticated malware known as ”AUTHENTIC ANTICS” to the cyber threat group APT 28, a known russian intelligence operation.
Unmasking APT 28 and the Sophistication of “AUTHENTIC ANTICS”
The NCSC, a vital part of GCHQ (Government Communications Headquarters), has for the first time publicly identified APT 28 as the perpetrator behind the “AUTHENTIC ANTICS” malware. this attribution marks a significant step in exposing the cyber operations of Russian intelligence services.
“The National Cyber Security Centre – a part of GCHQ – has revealed for the first time that the cyber threat group APT 28 has been responsible for deploying a sophisticated malware dubbed AUTHENTIC ANTICS as part of its operations,” the NCSC stated.
This attribution has also led to the UK Government sanctioning three GRU units (26165, 29155, and 74455) and 18 Russian individuals involved in these and other related campaigns.
Hybrid Operations and Growing Sophistication
UK officials have strongly condemned the actions of these GRU agents, characterizing their operations as hybrid warfare aimed at destabilizing Europe and posing a direct threat to British citizens. The deployment of ”AUTHENTIC ANTICS” is seen as a clear indicator of the Russian intelligence service’s increasing sophistication in cyber warfare.
At the same time, they underlined the NCSC’s unwavering commitment to exposing these cyber activities and holding the responsible parties accountable through sanctions.
“AUTHENTIC ANTICS” has been utilized in attacks since… (The provided text cuts off here, leaving the exact start date of its deployment unspecified).
