Bivash Nayak
25 Jul
25Jul

Posted by CyberDudeBivash on July 25, 2025

Hey, cyber guardians! Welcome back to CyberDudeBivash.com, your trusted ally in navigating the ever-evolving world of cybersecurity threats and defenses. Today, we're zeroing in on a high-stakes escalation that's shaking up enterprise security: Microsoft has warned that hackers exploiting vulnerabilities in on-premises SharePoint Server are now deploying ransomware on compromised systems. This development, detailed in a Microsoft security blog on July 22, 2025, highlights how initial access via flaws like CVE-2025-53770 is being leveraged for destructive payloads, affecting hundreds of organizations worldwideβ€”including U.S. agencies. If you're managing SharePoint environments, this is your signal to patch up prontoβ€”let's break it down, machas!

The Escalation: From Exploitation to Ransomware Onslaught

The story starts with CVE-2025-53770, a critical deserialization of untrusted data vulnerability (CVSS 9.8) in Microsoft SharePoint Server that allows unauthenticated remote code execution (RCE). Often chained with CVE-2025-53771 (a spoofing flaw, CVSS 6.5), attackers can bypass authentication, steal MachineKeys for persistent access, and deploy webshells like spinstall0.aspx. Exploitation began as early as July 7, 2025, initially for espionage by Chinese nation-state actors like Linen Typhoon (APT5) and Violet Typhoon (APT18).But here's the twist: Starting July 18, 2025, the China-linked threat actor Storm-2603 has been observed deploying ransomware using these vulnerabilities. This marks a shift from data theft to destructive encryption, with attackers using stolen keys to forge cookies, impersonate users, and modify Group Policy Objects (GPOs) for ransomware delivery. Ransomware variants like Warlock are being used, encrypting files and demanding payment while threatening data leaks.This escalation affects on-premises SharePoint 2016, 2019, and Subscription Editionβ€”cloud versions (SharePoint Online) are unaffected. Over 75 organizations have been breached so far, with mass attacks scanning for vulnerable servers.

Breaking Down the Vulnerabilities and Attack Chain

Let's get into the nuts and bolts:

  • CVE-2025-53770 (RCE via Deserialization): Allows unauthenticated attackers to execute arbitrary code by sending crafted requests to deserialize untrusted data. Often exploited via the ToolPane endpoint.
  • CVE-2025-53771 (Spoofing/Path Traversal): Enables bypassing of authentication checks, often chained with the above for initial access.

The typical attack chain:

  1. Initial Access: Unauthenticated POST requests exploit deserialization to upload webshells (e.g., .aspx files in /TEMPLATE/LAYOUTS/).
  2. Persistence: Steal MachineKeys to forge authentication cookies, bypassing MFA and allowing indefinite access even post-patch.
  3. Escalation to Ransomware: Deploy payloads via modified GPOs or scripts, encrypting data and demanding ransom.

IOCs include suspicious .js/.dll files, hashes like 92bb4ddb98eeaf11fc15bb32e71d0a63256a0ed826a03ba293ce3a8bf057a514 for webshells, and unusual IIS processes.

The Impacts: Widespread Breaches and Operational Chaos

This isn't just theoreticalβ€”hundreds of organizations, including U.S. agencies like the National Nuclear Security Administration (NNSA), have been hit. While no classified data was lost at NNSA, the breaches have led to:

  • Data Theft and Exposure: Sensitive infrastructure details exfiltrated for espionage.
  • Ransomware Disruptions: Systems encrypted, causing outages in energy, telecom, and finance sectors.
  • Broader Risks: Persistent access could enable lateral movement to integrated services like Teams or Outlook.
  • Global Scale: Over 8,000 exposed servers vulnerable, with attacks bypassing initial patches.

The shift to ransomware amplifies financial and operational damages, with recovery costs soaring for unpatched victims.

Microsoft's Response: Patches, Guidance, and Disruptions

Microsoft acted swiftly with out-of-band patches on July 19, 2025, for supported versions (KB5002754 for 2019, etc.). CISA added CVE-2025-53770 to its Known Exploited Vulnerabilities (KEV) catalog on July 20, mandating federal agencies to patch by August 10.Key guidance:

  • Patch and Rotate: Apply updates, then rotate MachineKeys via PowerShell (Set-SPMachineKey) and restart IIS.
  • Enable Protections: Turn on Antimalware Scan Interface (AMSI) in Full Mode and Microsoft Defender.
  • Hunt for Compromise: Use EDR queries to scan for IOCs; isolate unpatched servers.
  • Migrate if Possible: Move to SharePoint Online for built-in protections.

Microsoft also disrupted actor infrastructure, but exploitation continues.

Lessons Learned: Bolstering Defenses Against Evolving Threats

This saga teaches us:

  1. Patch Promptly: Zero-days like this evolve quicklyβ€”don't delay updates.
  2. Key Management: Always rotate secrets post-breach; use HSMs for critical keys.
  3. Runtime Monitoring: Deploy tools like EDR for in-memory threats.
  4. Zero-Trust Approach: Assume breach; segment networks and enforce MFA.
  5. Backup and Recovery: Test offline backups to avoid ransomware payouts.

At CyberDudeBivash.com, we recommend scanning tools like Nessus for SharePoint vulns and integrating runtime protection.

Wrapping Up: Don't Let SharePoint Become Your Weak Link

The jump from exploits to ransomware in SharePoint attacks is a game-changer, putting unpatched systems at extreme risk. As Microsoft and CISA sound the alarm, it's time to audit your environments and act fast.What are your thoughtsβ€”seen similar issues in your org? Share in the comments, and subscribe for more cyber alerts!Stay secure, machas! πŸ”’Sources: Microsoft Security Blog, MSRC Blog, Unit 42 (Palo Alto Networks), CISA Alerts, Trend Micro Research, The Hacker News, NVD, Reddit (r/cybersecurity).

Comments
* The email will not be published on the website.