

Multiple Apple macOS Sonoma Vulnerabilities
April 23, 2025
Hackers Weaponize Word Documents Using 17-Year-Old Vulnerability – Active IOCs
April 23, 2025
Multiple Apple macOS Sonoma Vulnerabilities
April 23, 2025
Hackers Weaponize Word Documents Using 17-Year-Old Vulnerability – Active IOCs
April 23, 2025Severity
High
Analysis Summary
Since early March 2025, Russian-linked threat actors, identified as UTA0352 and UTA0355, have launched a sophisticated campaign targeting individuals and organizations connected to Ukraine and human rights initiatives. These attacks stand out due to their exploitation of legitimate Microsoft OAuth 2.0 authentication workflows, allowing the actors to bypass traditional phishing detection techniques. Rather than hosting fake login pages, the campaign leverages Microsoft’s own infrastructure, ensuring that all user interactions occur within trusted domains and making the malicious activity far more difficult to detect.
The attack begins with highly targeted social engineering tactics via secure messaging platforms like Signal and WhatsApp. Impersonating government officials from Ukraine, Bulgaria, Romania, or Poland, the attackers establish trust with victims through plausible invitations to video conferences or meetings. In one case, they even used a compromised Ukrainian government account to bolster credibility. Once trust is secured, the victims are sent Microsoft login URLs that, when clicked, generate OAuth authorization codes. The attackers then request these codes under various pretexts, and if shared, they convert them into access tokens for full access to the victim’s Microsoft 365 (M365) account.
Beyond gaining access, the attackers move strategically to entrench themselves within the victim’s environment. In some instances, they use the stolen tokens to register new devices to the victim's Microsoft Entra ID (formerly Azure AD), creating persistent backdoors.

After breaching the accounts, Researchers observed the threat actors downloading emails and accessing sensitive information, all while masking their operations through geo-matched proxy networks to avoid triggering security alerts. This sophisticated use of Microsoft services marks a significant evolution in adversarial tactics, emphasizing stealth and persistence.
The campaign highlights critical vulnerabilities in trust-based systems and underscores the importance of user education and technical safeguards. Researchers recommend that organizations train users to be cautious of unsolicited secure messaging contacts and avoid sharing OAuth codes or suspicious URLs. Additionally, enforcing conditional access policies that restrict login access to pre-approved devices can help mitigate such threats. This marks the second instance in 2025 where Russian actors have employed unconventional techniques to breach M365 environments, reinforcing the urgent need for proactive defense strategies among at-risk sectors.
Impact
- Sensitive Information Theft
- Security Bypass
- Unauthorize Access
Remediation
- Instruct users never to share OAuth authorization codes or click suspicious Microsoft login URLs received via messaging apps.
- Implement Conditional Access Policies in Microsoft Entra ID (formerly Azure AD) to Restrict access only to managed or compliant devices and Enforce sign-in risk policies and location-based restrictions.
- Enable Multi-Factor Authentication (MFA) for all accounts to add an extra layer of protection against unauthorized access.
- Monitor OAuth consent grants in your Microsoft 365 environment for unusual or suspicious activity.
- Audit device registrations regularly to detect and remove unauthorized or suspicious devices.
- Use Identity Protection policies to detect risky sign-ins and users with compromised credentials.
- Apply strict app permissions and consent policies, only allowing trusted applications to request high-privilege OAuth scopes.
- Leverage Microsoft Defender for Cloud Apps to detect anomalous behavior or OAuth abuse.
- Establish geo-fencing rules to flag or block logins from unexpected regions, even if routed through proxies.