Extradited Russian Hacker Faces Charges Over Excel Malware Campaign That Infected Thousands
Extradited Russian Hacker Faces Charges Over Excel Malware Campaign That Infected Thousands. Searzhudin Tamirlanovich Aktulaev, 40, was arrested in Cyprus in May 2025, the U.
What happened
Extradited Russian Hacker Faces Charges Over Excel Malware Campaign That Infected Thousands. Department of Justice (DoJ) has charged a Russian national, extradited from Cyprus on August 28, with using roughly 255 fake accounts on a freelance platform to send malware-laced Excel attachments to about 80,000 of its users in 2016 and 2017. Searzhudin Tamirlanovich Aktulaev, 40, was arrested in Cyprus in May 2025, the U.
Threat reporting can develop quickly as vendors, governments and affected organizations publish new indicators and technical findings.
Editorial note: this News Brief follows the available evidence and adds length only when additional facts or useful context are available. Where public reporting does not establish a specific victim sequence, CyberDeltaForce does not present one as fact.
What the reporting and advisory establish
Department of Justice (DoJ) has charged a Russian national, extradited from Cyprus on August 28, with using roughly 255 fake accounts on a freelance platform to send malware-laced Excel attachments to about 80,000 of its users in 2016 and 2017.
Extradited Russian Hacker Faces Charges Over Excel Malware Campaign That Infected Thousands
What this means for your environment
Move from the published facts to the technical path, exposure conditions and defensive decisions that matter in a real environment.
Attack & Exploitation Path
The sequence below reconstructs the intrusion from the stages supported by public reporting. Undisclosed transitions remain explicitly marked rather than inferred.
Not publicly disclosed in the available reporting; CyberDeltaForce does not infer an entry method without evidence.
malware, a backdoor, loader, web shell or another persistent access mechanism is identified in the intrusion.
Validate the reported access path against identity, endpoint, network and cloud telemetry; contain confirmed footholds; remove exposed credentials or persistence; and prioritize the earliest stage where your controls can reliably break the chain.
Why this matters to you
The significance depends on whether the organizations, technologies or threat behavior in this story intersect with your environment. The useful next step is to compare the reported facts with your own exposure, suppliers and current threat model.
Does this deserve attention in my environment?
Check the conditions below against your use of the affected technology or service.
Select the conditions that are true in your environment. Leaving a condition unselected does not mean you are safe — it only means you have not marked it as applicable.
- Check whether the organizations, technologies or suppliers in the story are relevant to your environment.
- Review the retained primary source and any vendor or government guidance before changing controls.
- Increase monitoring if the reporting indicates active exploitation, material disruption or a threat path you use.
Sources & References
Original reporting and technical references are kept here for readers who want to verify the facts. Publisher names stay out of the reading flow above.