1-minute read
What a defender needs to know
The ransom family changed, but the access pattern persisted. In a September 24 investigation, Microsoft Threat Intelligence tracked Storm-2570 across Qilin, DragonForce, Anubis and BERT deployments. The affiliate repeatedly used remote-management agents, domain credential theft, lateral movement and cloud-transfer tools before encryption. Microsoft has not confirmed its first foothold; hunt the observed post-compromise trail.
Start with new or renamed meshagent64 services and binaries, especially victim-themed names. Correlate MeshAgent or Atera activity with ntdsutil.exe IFM copies of NTDS.dit on domain controllers, PsExec host lists such as @ip.txt, changes to Defender real-time protection or the C:\PerfLogs exclusion, and s5cmd.exe with a credentials file or Rclone. Microsoft’s examples use DeviceProcessEvents, DeviceFileEvents and DeviceRegistryEvents. These tools also have legitimate uses, so compare the installing account and timing with approved administration.
Remove unauthorized remote agents and outbound tunnel services after preserving evidence; revoke their access and reset the installing accounts’ passwords. Enable tenant-managed tamper protection and verify the endpoint’s effective settings, including exclusions. Pilot the Block process creations originating from PSExec and WMI commands ASR rule where compatible. Confirm that only approved RMM services remain, protected Defender settings are effective, and new unauthorized tunnel or cloud-copy processes stop after containment. A payload-only hunt starts too late.