Six well-known cyber threat actors and what defenders can learn
A practical guide to Scattered Spider, LockBit, Fancy Bear, Midnight Blizzard, Volt Typhoon, and TraderTraitor, with public sources and defensive priorities.
How to read a threat actor name
A threat actor name is a label used to group activity that researchers assess as related. Different organizations can give overlapping activity different names. A label can also describe a particular campaign, an affiliate operation, or a government-linked group. The six examples below are widely documented and illustrate different objectives. When reading an advisory, check who made the attribution, what activity it covers, and what that source actually confirmed.
Scattered Spider and identity recovery
A joint FBI and CISA advisory describes Scattered Spider as a financially motivated threat group linked to data extortion and known for social engineering. For defenders, the advisory makes identity recovery worth reviewing alongside ordinary sign-in. Check who can approve a password reset for a privileged account, what evidence is required before an authentication factor is replaced, and whether a second person reviews sensitive changes. Correlate help-desk records with identity logs so an unusual recovery request can be investigated in context.
LockBit and the ransomware affiliate model
LockBit is a ransomware operation that supplied tools and services to affiliates. The U.S. Department of Justice and its partners announced a disruption of the operation in February 2024. The affiliate structure matters when interpreting incidents because different people can use the same ransomware brand. Make recovery measurable. Restore a representative service from an isolated backup, verify that it runs with known-good identity and configuration, and measure the time until the service is usable.
Fancy Bear and Midnight Blizzard
The U.S. Department of Justice associates Fancy Bear, also called APT28, with a unit of Russia’s military intelligence service. CISA identifies Midnight Blizzard with Russia’s Foreign Intelligence Service and describes targets that include government networks, policy organizations, and technology companies. Microsoft’s naming guide maps Midnight Blizzard to activity also tracked as APT29. Use the specific advisory to understand which group is being discussed. Review unusual access to sensitive email, repositories, and identity systems, and keep audit records long enough to reconstruct account activity.
Volt Typhoon and critical infrastructure
A joint advisory attributes Volt Typhoon activity to actors sponsored by the People’s Republic of China. The agencies assessed that the activity aimed to establish access that could enable future disruption in critical infrastructure. That assessment concerns the purpose of the access. Its relevance to an operator depends on how business IT connects to operational systems. Map those connections, document approved remote administration paths, and verify that operational teams can detect and investigate changes to access.
TraderTraitor and North Korean cryptocurrency theft
The FBI attributed the February 2025 theft of approximately $1.5 billion in virtual assets from Bybit to North Korea and called that specific activity TraderTraitor. For teams operating digital asset services, the case is a reason to review the authorization workflow around sensitive transfers. In a controlled exercise, check that approvers can independently verify the destination and amount and that a single compromised workstation cannot satisfy every approval requirement.
What AI teams can do with these examples
Map the same defensive questions to your own environment. Who can recover an administrator account? Which vendors and integrations can reach private repositories or training data? Can you restore a model-serving workload from a trusted version and revoke a provider key without an outage? During an investigation, record timestamps, account changes, affected resources, and verified outcomes first. Compare the evidence with public reporting to guide the next checks. Shared behavior alone provides weak evidence for attributing an incident to a named group.