osec.one case analysis cover: GoAnywhere MFT 2025 forged license response and Medusa ransomware

GoAnywhere MFT's 2025 incident began in a component that looks operational rather than dangerous: the License Servlet in its administration console. CVE-2025-10035, scored 10.0, allowed a forged license-response signature to bypass verification and reach deserialization of an attacker-controlled object. Microsoft says Storm-1175 was exploiting the zero-day on 11 September 2025; Fortra disclosed it on 18 September. Microsoft observed the group use the access to place remote-management tools under the GoAnywhere process, create JSP files, map networks, use remote desktop and Rclone, and deploy Medusa ransomware in one compromised environment.

The case is a useful correction to an easy assumption: an MFT server is not merely an encrypted mailbox. It often has a public listener, an administration layer, service accounts, automated jobs and reach into partner or internal storage. When an unauthenticated management bug becomes code execution, the MFT host must be handled as an internet-facing application server and a potential identity pivot.

Six-step diagram: License Servlet, forged signature, attacker-controlled deserialization, RMM and JSP persistence, discovery/tunnel/Rclone, Medusa ransomware

What happened, dated

WhenObserved or published eventWhy it matters
11 Sep 2025Microsoft observes related activityThe exploitation preceded the public advisory by 7 days.
18 Sep 2025Fortra publishes its advisory for CVE-2025-10035Customers get the patch signal after the zero-day window.
6 Oct 2025Microsoft publishes the Storm-1175 investigationIt records a full intrusion path rather than only a theoretical CVE impact.
2026 follow-upMicrosoft says Storm-1175 used CVE-2025-10035 one week before disclosureExternal inventory and fast containment matter when a perimeter product is newly disclosed.

Why a forged license response became code execution

Licensing systems commonly receive a signed object and verify it before reading its contents. The defect reversed the trust boundary: a forged signature could pass the License Servlet's validation stage, and the server then deserialized an object supplied by the requester. Java deserialization is risky because object construction can invoke application or library behavior during the read. The public advisories describe the result as command injection and potential remote code execution; this article deliberately does not provide an exploit payload or construction sequence.

LayerWhat Storm-1175 didDefender check
Initial accessExploited the License Servlet deserialization flawConfirm every console is on the vendor-fixed version and not internet-reachable unless unavoidable
PersistenceDropped SimpleHelp and MeshAgent beneath the GoAnywhere MFT process; created JSP filesBaseline MFT directories; alert on new JSPs and RMM binaries executed by its service account
DiscoveryRan user/system commands and netscanLook for command-shell children, netscan and unusual account/group enumeration
Movement and C2Used mstsc.exe, RMM and a Cloudflare tunnelReview new remote tools, services, scheduled tasks and outbound tunnelling destinations
Exfiltration/objectiveUsed Rclone in at least one victim; Medusa in one observed environmentReview archive creation, Rclone config/processes and large unusual outbound transfers

The first day: patching is necessary, not a clean bill of health

Microsoft explicitly notes that upgrading does not address prior exploitation. Treat the following as a contained incident workflow for a vulnerable, exposed system:
1. Preserve evidence and isolate deliberately. Save application, web and endpoint logs before rotating or rebuilding. Restrict the administration interface to a management network or VPN while transfer dependencies are mapped.
2. Upgrade to Fortra's current fixed release. Verify the installed build afterwards from the product's own console or package inventory, not only a change ticket.
3. Hunt the product tree and service context. Look for JSP files added in GoAnywhere directories, RMM binaries (Microsoft names SimpleHelp and MeshAgent), unfamiliar services and scheduled tasks.
4. Follow the observed path outward. Search endpoint telemetry for netscan, mstsc.exe, Rclone, newly created local administrators and tunnel tooling around the MFT service account's activity window.
5. Rotate what the MFT server could read. This includes local administrators, database/storage credentials, SFTP keys, partner credentials and any secrets in automated workflows. Rebuild the host if integrity cannot be established.

Exposure is an architectural decision

Partners may need a public transfer endpoint; they do not normally need a public administration console. Put transfer and management on separate interfaces or reverse-proxy rules, permit management only from a small allowlist, and inventory every hostname that can lead to the product. The osec Site protection scan is a harmless outside check for the WAF/CDN and header posture in front of a public hostname; it cannot prove an MFT console is safe or discover a private management address.

Why this belongs with the file-transfer cases

CrushFTP 2025 shows an authentication mistake turning a public file-transfer service into administration access. MOVEit Transfer 2023 is the larger reminder that automated transfer servers aggregate valuable partner data. The common defense is not one brand-specific setting: minimise exposed management surfaces, patch on an exploitation timeline, and assume the service account's reachable secrets are part of the blast radius.

Check what protection and security headers a public hostname actually exposes, without installing an agent or changing DNS.

Run a site protection scan

Sources

• Microsoft Security, Investigating active exploitation of CVE-2025-10035 (6 Oct 2025): https://www.microsoft.com/en-us/security/blog/2025/10/06/investigating-active-exploitation-of-cve-2025-10035-goanywhere-managed-file-transfer-vulnerability/
• Microsoft Security, Storm-1175 high-tempo operations (6 Apr 2026): https://www.microsoft.com/en-us/security/blog/2026/04/06/storm-1175-focuses-gaze-on-vulnerable-web-facing-assets-in-high-tempo-medusa-ransomware-operations/
• CVE Program record: https://www.cve.org/CVERecord?id=CVE-2025-10035
• NIST NVD record: https://nvd.nist.gov/vuln/detail/CVE-2025-10035
• Fortra advisory and upgrade guidance: https://www.fortra.com/security/advisory/fi-2025-012