Russian APTs: OAuth Abuse, RDP Phish, and Takedowns

Russia-linked actors leaned hard on OAuth device codes and RDP phishing from Oct 2024–Aug 2025. Providers pushed back in concert. Here’s what changed, what to watch in your logs, and the quickest moves that buy real risk reduction.

Share
Russian APTs: OAuth Abuse, RDP Phish, and Takedowns
Welcome to the Device-Code Bazaar: buy one phish, get a token free. No refunds after lateral movement.

TL;DR

Key Points

  • Block the top entry vectors by tightening OAuth “device code” flows and stripping risky legacy auth; this cuts credential theft and cloud takeovers.

  • Enforce phishing-resistant MFA (FIDO2/WebAuthn) to stop token theft at the gate; legacy MFA is not enough.

  • Hunt for malicious RDP file delivery and sudden cloud app consent spikes; these are reliable early tells.

  • Automate intel sharing and takedown playbooks with your vendors; faster disruption forces the adversary to burn time.

  • Plan for rapid actor adaptation with policy guardrails (tenant restrictions, consent governance) so pivots don’t become new gaps.

Jargon quick-defs: OAuth = token-based delegated access standard; MFA = multi-factor authentication; TTPs = tactics, techniques, and procedures.

The story in 60 seconds

From 2023–2025, APT29 (Midnight Blizzard), APT28 (Fancy Bear), and Sandworm pressed cloud identity weaknesses and classic social engineering. Two anchor events: an Oct 2024 spear-phish wave delivering weaponized .rdp files, and an Aug 2025 watering-hole using OAuth device code prompts to snatch tokens and move laterally.

What was different this time was defense. Cloud, social, and infrastructure providers aligned on data sharing and takedowns, compressing the attackers’ dwell time. That forced rapid infrastructure rotation and cost.

Sectors hit: government, cloud platforms, and critical infrastructure. Techniques mapped cleanly to MITRE ATT&CK: T1528 (OAuth abuse), T1566.002 (spear-phishing), T1021.001 (RDP), T1190 (web injection), T1486 (ransomware/wipers), T1583.001 (infra acquisition).


AlphaHunt

Stop doomscrolling, start decisioning. We chewed through the muck so your team doesn’t have to. → Subscribe! • Forward to your on-call lead.

(Have feedback? Did something resonate with you? Did something annoy you? Just hit reply! :))


See it in your telemetry

Network

  • Outbound to unusual OAuth/identity endpoints or newly registered cloud apps; anomalous device code grant flows.
  • TLS to short-lived domains linked from watering-holes; sudden DNS churn tied to consent URIs.
  • RDP traffic spikes from non-management subnets.

Endpoint

  • New or modified “Remote Desktop” connection files and MSTSC invocations with embedded creds/addresses.
  • Browser token store access, abnormal OAuth refresh activity, and new device identities enrolling outside business hours.
  • Suspicious PowerShell/Office child-process chains post-phish.

Mail/IdP/SaaS

  • Delivery of .rdp attachments/links; lure themes tied to IT help or SSO resets.
  • “Consent to application,” “Service principal created,” “Enterprise app added,” scope elevations, or mass token issuance.
  • Admin approval requests originating from atypical geo/ASN.

High Impact, Quick Wins

  • Lock down device code flows (today): Require managed/compliant device and step-up MFA for sensitive scopes; disable for high-risk users. Sell it: Stops no-prompt token theft. Measure it: Reduction in device code grants from unmanaged endpoints and geo-anomalies.

  • Move to phishing-resistant MFA (this quarter): FIDO2/WebAuthn for all admins and Tier-0 apps; phase to all users. Sell it: Cuts token replay and push fatigue. Measure it: % users on FIDO2; drop in MFA push prompts.

  • Govern consent and app registration (this sprint): Admin-only consent, verified publishers, and tenant restrictions. Sell it: Removes one-click data exfil paths. Measure it: Zero unreviewed enterprise apps; time-to-revoke token ≤15 minutes.


AlphaHunt

CTA Image

Ready to level up your intelligence game?

Sign Up!

Breaches

(Breach Date 2025-08) – Amazon, Microsoft, and Cloudflare Disrupt APT29 (Midnight Blizzard) Watering Hole Campaign

Description:
In August 2025, Amazon, Microsoft, and Cloudflare collaborated to disrupt a Russian state-sponsored campaign by APT29 (Midnight Blizzard/Cozy Bear). Attackers compromised legitimate websites, injecting JavaScript to redirect a subset of visitors to attacker-controlled domains mimicking Cloudflare and Microsoft authentication pages. The goal was to trick users into authorizing attacker-controlled devices via Microsoft’s device code authentication flow, granting access to Microsoft 365 accounts and sensitive data. Amazon’s threat intelligence team identified the infrastructure, isolated malicious EC2 instances, and, in partnership with Microsoft and Cloudflare, seized domains and blocked traffic. The campaign demonstrated APT29’s evolving tradecraft, including rapid infrastructure migration and advanced evasion techniques.

Technical Analysis:

  • Attack vector(s): Watering hole attacks, JavaScript injection, device code phishing, OAuth abuse.
  • Mitigation techniques: Domain seizure, infrastructure isolation, cross-provider intelligence sharing, user notification, authentication hardening.
  • Inter-provider protocols: Real-time intelligence sharing, joint infrastructure takedown, coordinated public advisories.
  • Impact: The disruption immediately halted credential theft, forced APT29 to rapidly migrate infrastructure, and exposed their evolving TTPs. The campaign’s exposure led to increased vigilance and improved detection rules across the ecosystem.
  • Lessons learned: Persistent, cross-provider response is essential; adversaries adapt quickly, requiring ongoing monitoring and collaboration.

Actionable Takeaways:

  1. Implement strict OAuth and device code authentication policies; monitor for anomalous device authorizations.
  2. Establish and maintain cross-provider threat intelligence sharing protocols for rapid response.
  3. Educate users on verifying authentication prompts and recognizing social engineering tactics.
  4. Harden cloud and web infrastructure against JavaScript injection and domain abuse.

Impact:
After the takedown, APT29 attempted to migrate to new infrastructure, but the rapid, coordinated response forced them to expend additional resources and delayed further credential theft. The exposure of their TTPs led to improved detection and prevention across the cloud ecosystem.


2. (Breach Date 2024-10) – Microsoft, Amazon, and CERT-UA Disrupt Midnight Blizzard (APT29) RDP Spear-Phishing Campaign

Description:
In October 2024, Microsoft, Amazon, and Ukraine’s CERT-UA identified and disrupted a spear-phishing campaign by APT29 targeting government, defense, and NGO sectors globally. The campaign used highly targeted emails with malicious, signed RDP configuration files, which, when opened, connected victims’ devices to attacker-controlled servers, exposing credentials and enabling malware installation. The campaign leveraged compromised email infrastructure and referenced multiple cloud providers in phishing lures. Microsoft and Amazon shared indicators of compromise, detection rules, and coordinated notifications to affected organizations.

Technical Analysis:

  • Attack vector(s): Spear-phishing with malicious RDP files, credential harvesting, lateral movement via cloud trust chains.
  • Mitigation techniques: Automated detection and blocking of malicious RDP files, endpoint and email security hardening, user education, cross-provider notification.
  • Inter-provider protocols: Joint publication of IOCs, hunting queries, public advisories, direct customer notifications.
  • Impact: The disruption prevented further credential theft and lateral movement, and the rapid sharing of IOCs improved detection across multiple providers. APT29 shifted to new phishing lures and infrastructure, but the ecosystem’s response time improved.
  • Lessons learned: Attackers exploit trust in cloud and email ecosystems; rapid, transparent cross-provider response is critical.

Actionable Takeaways:

  1. Block or restrict outbound RDP connections to external networks.
  2. Deploy advanced anti-phishing and endpoint detection solutions.
  3. Use phishing-resistant MFA and conditional access policies.
  4. Share IOCs and detection rules across providers and sectors.

Impact:
The campaign’s exposure led to a measurable reduction in successful spear-phishing attempts and improved detection speed for similar TTPs.


3. (Breach Date 2023-2025) – APT28 (Fancy Bear) Disruption: Meta, Cloudflare, and Partners

Description:
From 2023–2025, Meta (Facebook), Cloudflare, and partners collaborated to disrupt APT28’s credential theft and influence operations targeting Western logistics, technology, and maritime supply chains supporting Ukraine. APT28 used phishing, backdoors (e.g., NotDoor), and domain impersonation to compromise targets. Meta’s quarterly threat reports and Cloudflare’s technical advisories detail the use of automated account and domain takedown, legal action, and public transparency reports. Cloudflare and Meta shared real-time abuse data, coordinated legal filings, and published joint advisories.

Technical Analysis:

  • Attack vector(s): Social media phishing, domain impersonation, backdoor malware (e.g., NotDoor), supply chain compromise.
  • Mitigation techniques: Automated account and domain takedown, legal action, public transparency reports, technical detection rules (e.g., Sigma rules for NotDoor).
  • Inter-provider protocols: Real-time abuse reporting, joint legal filings, automated threat intelligence feeds, public advisories.
  • Impact: The disruption reduced the reach of APT28’s campaigns, forced the group to rotate infrastructure more frequently, and improved user protection. The legal and technical frameworks enabled rapid cross-jurisdictional action.
  • Lessons learned: Legal and policy frameworks are essential for rapid, cross-jurisdictional action; technical detection rules must be updated as adversaries adapt.

Actionable Takeaways:

  1. Establish legal agreements for rapid domain and account takedown.
  2. Share abuse data and threat intelligence in real time.
  3. Publish regular transparency reports to inform the public and ecosystem.

Impact:
After disruptions, APT28 shifted to new malware variants and infrastructure, but the frequency and impact of successful campaigns decreased, and detection speed improved.


4. (Breach Date 2023-2025) – Sandworm (APT44) and Hybrid State-Criminal Operations: Google TAG, Mandiant, and Partners

Description:
Google TAG, Mandiant, and partners have tracked and disrupted Russian GRU-linked Sandworm (APT44) operations targeting Ukraine and Europe. Sandworm leveraged commodity malware, ransomware, and wipers (e.g., NotPetya, Prestige) sourced from cybercrime communities. Cross-provider efforts included rapid takedown of malicious domains, sharing of IOCs, and coordinated public advisories. Google TAG’s transparency reports and joint advisories with government agencies highlighted the importance of multi-vendor collaboration and the blending of state and criminal TTPs.

Technical Analysis:

  • Attack vector(s): Phishing, commodity malware (e.g., SmokeLoader, RADTHIEF), ransomware, destructive wipers, domain abuse.
  • Mitigation techniques: Domain takedown, automated threat intelligence sharing, public-private joint advisories, technical detection rules.
  • Inter-provider protocols: Automated feeds, joint task forces, legal mechanisms for domain seizure, public advisories.
  • Impact: Disruptions forced Sandworm to rely more on criminal toolkits, increased operational costs, and improved victim protection. The blending of state and criminal TTPs complicated attribution but also exposed operational dependencies.
  • Lessons learned: Persistent, multi-vendor collaboration is required to counter adaptive state actors; technical and legal frameworks must evolve to address hybrid threats.

Actionable Takeaways:

  1. Participate in automated threat intelligence sharing platforms.
  2. Coordinate with government and industry partners for rapid takedown.
  3. Maintain transparency with public advisories and victim notifications.

Impact:
Sandworm’s reliance on criminal infrastructure increased after disruptions, but the frequency and impact of successful attacks decreased, and detection speed improved.


5. (Breach Date 2023-2025) – ISAC/CERT-Led Public-Private Disruptions (Multiple Sectors)

Description:
Sector-specific Information Sharing and Analysis Centers (ISACs), CERTs, and public-private partnerships have played a critical role in disrupting state-sponsored campaigns across healthcare, finance, and energy. These models leverage automated intelligence sharing, joint incident response, and coordinated legal action to reduce risk and impose costs on adversaries. The FS-ISAC 2024 report details frameworks for cryptographic agility, transition governance, and technical protocols for sector-wide resilience.

Technical Analysis:

  • Attack vector(s): Sector-specific phishing, ransomware, supply chain attacks, cryptographic vulnerabilities.
  • Mitigation techniques: Automated threat feeds, joint incident response, sector-wide advisories, cryptographic agility frameworks, technical playbooks.
  • Inter-provider protocols: ISAC platforms, CERT coordination, government-industry task forces, technical standards for cryptographic agility.
  • Impact: Faster detection and response, reduced victim impact, and increased adversary deterrence. Legal harmonization and technical standards remain ongoing challenges.
  • Lessons learned: Ecosystem-wide collaboration is essential for resilience; legal harmonization and technical standards are critical for rapid cross-border action.

Actionable Takeaways:

  1. Join and actively participate in sector ISACs and CERTs.
  2. Develop joint playbooks for incident response and legal action.
  3. Advocate for harmonized legal frameworks and technical standards.

Impact:
ISAC/CERT-led disruptions have led to measurable reductions in victimization, improved detection speed, and the evolution of public-private partnership models.


Recommendations, Actions, Suggested Pivots, Forecasts and Next Steps

(Subscribers Only)


Recommendations, Actions and Next Steps

1. Operationalize Automated, Standards-Based Threat Intelligence Sharing and Joint Response

Actions:

  • Deploy and integrate open standards for threat intelligence sharing, such as STIX/TAXII, across all participating organizations and cloud providers.
  • Adopt a platform like MISP (Malware Information Sharing Platform) for structured, real-time exchange of IOCs, TTPs, and detection rules.
  • Develop and maintain joint incident response playbooks using FS-ISAC or FIRST templates, specifying minimum data elements (e.g., IOCs, affected assets, response timelines, notification protocols).
  • Establish quarterly cross-provider tabletop exercises to validate and update these playbooks, ensuring readiness for rapid, coordinated takedowns and victim notifications.

Expected Impact:

  • Accelerates detection and disruption of state-sponsored campaigns (e.g., APT29, APT28, Sandworm), as demonstrated by the immediate halt of credential theft and forced adversary infrastructure migration following the August 2025 APT29 disruption.
  • Reduces time-to-mitigate and increases the scope of ecosystem protection.

Challenges:

  • Legal and regulatory constraints on cross-border data sharing; technical integration with legacy SIEM/SOAR tools; need for ongoing trust and governance.

Metrics for Success:

  • Median time from IOC discovery to ecosystem-wide dissemination; number of joint takedowns executed; reduction in successful credential theft or phishing incidents post-collaboration; frequency and quality of playbook updates.

MITRE ATT&CK IDs: T1071, T1589, T1566, T1078


2. Accelerate Authentication Hardening and Cloud/Web Infrastructure Security with Measurable Milestones

Actions:

  • Mandate phishing-resistant MFA (e.g., FIDO2/WebAuthn) for all privileged and high-risk users within 30 days; track rollout and user compliance.
  • Enforce conditional access policies and continuous monitoring for anomalous device code authorizations in Microsoft 365 and other SaaS platforms.
  • Conduct a 60-day audit of all externally facing web assets for JavaScript injection and domain abuse vulnerabilities; remediate using CSP, SRI, and automated code scanning tools.
  • Implement quarterly reviews and updates of detection rules for OAuth abuse, device code phishing, and credential harvesting, leveraging Sigma rules and MITRE D3FEND mappings.

Expected Impact:

  • Directly addresses the attack vectors exploited by APT29 and APT28, as seen in the measurable reduction in credential theft and spear-phishing success rates post-disruption.
  • Increases resilience against evolving phishing and OAuth abuse techniques.

Challenges:

  • User friction and support overhead for MFA adoption; resource requirements for infrastructure audits; need for ongoing user education and awareness.

Metrics for Success:

  • Percentage of high-risk users enrolled in phishing-resistant MFA; number of anomalous device authorizations detected and blocked; time to remediate web vulnerabilities; frequency of detection rule updates and efficacy in blocking new TTPs.

MITRE ATT&CK IDs: T1556, T1110, T1190, T1056


Actions:

  • Require active participation in sector ISACs, CERTs, and public-private task forces; assign dedicated liaisons and ensure regular contribution to automated threat feeds and joint advisories.
  • Develop and maintain joint incident response and legal takedown playbooks, referencing FS-ISAC cryptographic agility frameworks and legal templates for rapid domain/account seizure.
  • Launch a quarterly transparency report detailing takedown actions, detection improvements, and cross-sector lessons learned; advocate for harmonized legal and technical standards at industry forums.
  • Begin a 90-day cryptographic inventory and agility assessment using FS-ISAC’s eight-phase framework, prioritizing high-risk assets and third-party dependencies.

Expected Impact:

  • Enables rapid, cross-jurisdictional disruption of hybrid state-criminal campaigns (e.g., Sandworm, APT28), as shown by the reduction in campaign reach and improved detection speed.
  • Builds long-term sector resilience and readiness for post-quantum threats.

Challenges:

  • Aligning legal requirements across jurisdictions; resource allocation for ongoing engagement; ensuring actionable, timely reporting and cryptographic modernization.

Metrics for Success:

  • Number of joint playbooks and legal agreements in place; time to execute legal takedowns; participation rate in ISAC/CERT activities; completion and maturity of cryptographic agility assessments.

MITRE ATT&CK IDs: T1489, T1486, T1583, T1584


Suggested Pivots

  1. Which specific technical components of cross-provider threat intelligence sharing—such as automated IOC exchange, real-time alerting mechanisms, or standardized joint incident response playbooks—are currently limiting the speed and effectiveness of disrupting adversary infrastructure migrations like those observed in APT29’s 2025 watering hole campaign? How can these components be enhanced to reduce adversary operational agility?

  2. What recent vulnerabilities or attack techniques related to OAuth and device code authentication flows have been exploited by APT29 and similar groups, and what concrete cloud and web infrastructure hardening measures (e.g., Content Security Policy enforcement, Subresource Integrity, automated JavaScript scanning) can be systematically implemented to mitigate JavaScript injection and domain abuse at scale?

  3. How can international legal and policy frameworks be harmonized to enable faster, coordinated takedown actions against hybrid state-criminal threat actors such as Sandworm (APT44)? What are the best practices for sector-specific ISACs and CERTs to institutionalize public-private collaboration, legal harmonization, and cryptographic agility to improve ecosystem-wide resilience?


Forecast

Short-Term Forecast (3-6 months)

  • APT29 Infrastructure Migration and Adaptation: Following the August 2025 disruption of APT29’s watering hole campaign by Amazon, Microsoft, and Cloudflare, APT29 will continue rapidly migrating infrastructure to new cloud providers and registering new domains to evade detection. This will increase operational complexity for defenders and require sustained cross-provider vigilance.

  • Institutionalization of Cross-Provider Collaboration: The success of the joint takedown and intelligence sharing among Amazon, Microsoft, and Cloudflare will drive more formalized and frequent cross-provider collaboration frameworks, including automated IOC sharing and coordinated public advisories, to accelerate disruption of state-sponsored campaigns.

  • Authentication Hardening and User Education: Organizations will accelerate deployment of phishing-resistant MFA (e.g., FIDO2/WebAuthn), enforce conditional access policies, and conduct targeted user education on recognizing device code phishing and malicious RDP file spear-phishing to reduce successful credential theft.

  • Sector-Specific ISAC and CERT Collaboration: Critical sectors such as finance, healthcare, and energy will intensify participation in ISACs and CERTs, leveraging automated threat feeds, joint incident response playbooks, and legal frameworks to reduce victim impact from ransomware and supply chain attacks.

Examples

  • APT29’s rapid infrastructure migration and domain registration after takedown.
  • Microsoft and Amazon’s coordinated disruption of APT29’s spear-phishing campaign using malicious RDP files.
  • FS-ISAC’s detailed cryptographic agility framework guiding sector-wide resilience.

What to watch out for

  • Detection of new domains mimicking cloud providers or authentication services, especially those linked to APT29.
  • Telemetry indicating anomalous device code authentication attempts or OAuth abuse from untrusted or new domains.
  • Uptake metrics of phishing-resistant MFA and conditional access policies in high-risk organizations.
  • Frequency and scope of joint cross-provider takedowns and public advisories.
  • Reports of successful credential theft or lateral movement despite enhanced mitigations.

Long-Term Forecast (12-24 months)

  • Maturation of Automated Cross-Provider Threat Intelligence Sharing: Expect widespread adoption of automated, standards-based platforms (e.g., STIX/TAXII, MISP) enabling near real-time, ecosystem-wide dissemination of IOCs, TTPs, and detection rules, significantly reducing adversary dwell time and operational success.

  • Legal and Policy Harmonization for Cross-Jurisdictional Takedowns: International cooperation and harmonization of legal frameworks will improve, enabling faster, coordinated takedown actions against hybrid state-criminal threat actors like Sandworm (APT44), increasing adversary operational costs and reducing campaign effectiveness.

  • Cryptographic Agility and Post-Quantum Readiness: Cryptographic agility will become a standard organizational requirement, with sectors completing comprehensive inventories and transitioning critical assets to quantum-resistant algorithms, mitigating future cryptographic vulnerabilities exploited by adversaries.

  • Adversary Evolution and Operational Constraints: While APT28, APT29, and similar groups will continue evolving TTPs—including supply chain compromises, domain impersonation, and OAuth abuse—their operational tempo and success rates will be constrained by improved detection, legal frameworks, and ecosystem resilience.

  • Institutionalization of Public-Private Partnerships: ISACs, CERTs, and public-private task forces will institutionalize joint incident response playbooks, transparency reporting, and legal frameworks, creating a resilient ecosystem capable of rapid adaptation to emerging threats and reducing victimization.

Examples

  • Multi-year disruption of APT28’s campaigns reducing phishing and supply chain attacks.
  • Google TAG and Mandiant’s joint advisories on Sandworm’s hybrid operations highlighting evolving legal and technical frameworks.
  • FS-ISAC’s comprehensive cryptographic agility framework guiding long-term sector readiness.

What to watch out for

  • Metrics on the number and speed of cross-border takedown requests and their execution times as indicators of legal harmonization progress.
  • Adoption rates and maturity levels of cryptographic agility programs, including post-quantum algorithm deployments.
  • Emergence of new adversary TTPs targeting supply chains, OAuth flows, or leveraging novel phishing techniques.
  • Frequency and impact of hybrid state-criminal campaigns and effectiveness of public-private partnership responses.
  • Transparency reports from ISACs and CERTs detailing ecosystem resilience improvements and joint incident response outcomes.

MITRE ATT&CK IDs

T1528, T1566.002, T1190, T1071, T1078, T1021.001, T1486, T1583.001, T1584, T1056, T1110, T1589, T1567, T1562, T1560


Appendix

References

  1. (2025-08-29) – Amazon Disrupts APT29 Watering Hole Campaign Abusing Microsoft Device Code Authentication | The Hacker News
  2. (2025-09-01) – Amazon disrupts Russian APT29 hackers targeting Microsoft 365 | BleepingComputer
  3. (2025-09-02) – Amazon Disrupts Russian APT29 Cyber Espionage with Microsoft, Cloudflare | WebProNews
  4. (2024-10-29) – Midnight Blizzard conducts large-scale spear-phishing campaign using RDP files | Microsoft Security Blog
  5. (2025-07-30) – Hacktivists, nation-state hackers target global maritime infrastructure as cyberattacks, GPS spoofing surge | Industrial Cyber
  6. (2025-05-22) – Detect APT28 Attacks: Russian GRU Unit 26156 Targets Western Logistics and Technology Companies Coordinating Aid to Ukraine | SOC Prime
  7. (2025-02-12) – Cybercrime: A Multifaceted National Security Threat | Google Threat Intelligence Group
  8. (2024-10) – Building Cryptographic Agility in the Financial Sector | FS-ISAC

AlphaHunt

Stop doomscrolling, start decisioning. We chewed through the muck so your team doesn’t have to. → Subscribe! • Forward to your on-call lead.

(Have feedback? Did something resonate with you? Did something annoy you? Just hit reply! :))

(c) 2025 CSIRT Gadgets, LLC


MITRE ATTACK

Techniques

  1. T1528 (Steal Application Access Token)

    • Directly tied to the August 2025 APT29 (Midnight Blizzard) watering hole campaign, where attackers abused OAuth device code authentication to access Microsoft 365 accounts. As reported: “Attackers compromised legitimate websites, injecting JavaScript to redirect a subset of visitors to attacker-controlled domains mimicking Cloudflare and Microsoft authentication pages...tricking users into authorizing attacker-controlled devices via Microsoft’s device code authentication flow.”
    • Amazon Disrupts APT29 Watering Hole Campaign Abusing Microsoft Device Code Authentication
  2. T1566.002 (Phishing: Spearphishing Link)

  3. T1190 (Exploit Public-Facing Application)

Tactics

  1. TA0001 (Initial Access)

  2. TA0006 (Credential Access)

  3. TA0040 (Impact)

Procedures

  1. T1021.001 (Remote Services: Remote Desktop Protocol)

  2. T1486 (Data Encrypted for Impact)

  3. T1583.001 (Acquire Infrastructure: Domains)

Software

  1. S0226 (SmokeLoader)

  2. S0368 (NotPetya)

Mitigations

  1. M1036 (Account Use Policies)

    • Enforce strong authentication, restrict device code authorizations, and monitor for anomalous OAuth activity to mitigate credential theft and abuse, as recommended after the APT29 watering hole campaign.
    • Account Use Policies - Enterprise | MITRE ATT&CK®
  2. M1021 (Restrict Web-Based Content)

  3. M1054 (Software Configuration)

Groups

  1. G0016 APT29 (Cozy Bear, Midnight Blizzard, NOBELIUM, UNC3524)

  2. G0007 APT28 (Fancy Bear, Sofacy, STRONTIUM, Sednit)

  3. G0034 Sandworm Team (APT44, Seashell Blizzard, Voodoo Bear)