Clop ransomware claims Suunto.com compromise
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
Clop ransomware operators claim breach of Suunto.com with exfiltrated data, affecting thousands of users and employees.
Ransomware.live, an aggregator of ransomware operator disclosures, reports that Clop ransomware operators claim responsibility for a breach of Suunto.com (the Chinese subsidiary). According to the posting, the incident involved compromise of employee credentials and exposure of user data. The claim indicates 1 compromised employee, 3,139 compromised users, 4 third-party employee credentials, and 101 DNS records associated with the victim's domain. The operators posted screenshots of exfiltrated data as proof. This appears to be a data exfiltration and extortion campaign typical of Clop's operating model, where operators threaten to publish stolen data unless a ransom is paid. Defenders should treat this as confirmation of a breach affecting the Suunto.com infrastructure and customer database.
Mentioned in this report
Detection guidance
Rclone-Style Bulk Data Transfer to Cloud Storage
Detects rclone (including renamed copies) being used to copy, sync or move data to a remote cloud storage backend, a common staging step for exfiltration before ransomware extortion. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.
title: Rclone-Style Bulk Data Transfer to Cloud Storage
description: Detects rclone, or a renamed binary using rclone-specific flags, copying/syncing/moving
data to a remote cloud storage backend. Generalises on the rclone subcommand and
flag pattern, not on any specific remote name or destination. The Clop report only
claims data theft and extortion, so this covers the exfiltration-to-cloud-storage
technique generically.
tags:
- attack.exfiltration
- attack.t1567.002
logsource:
category: process_creation
product: windows
detection:
selection_named:
- Image|endswith: \rclone.exe
- OriginalFileName: rclone.exe
selection_named_cmd:
CommandLine|contains:
- ' copy '
- ' sync '
- ' move '
- ' copyto '
selection_renamed:
CommandLine|contains|all:
- --transfers
- --no-check-certificate
selection_renamed_alt:
CommandLine|contains|all:
- --config
- --transfers
- ':'
condition: (selection_named and selection_named_cmd) or selection_renamed or selection_renamed_alt
falsepositives:
- Administrators or backup jobs legitimately using rclone to sync data to approved
cloud storage
- Developers using rclone for personal or project data transfers
level: medium
id: 89558025-e506-5e4d-bbda-e048c43c4093
status: experimental
author: Vorant
references:
- https://www.ransomware.live/id/U1VVTlRPLkNOKFNVVU5UTy5DT00pQGNsb3A=
2 more detections for this report are in the app — the rules that match its indicators, plus the Sigma rules already converted to Splunk SPL, to Elastic where their fields map onto Elastic's integrations and to Microsoft Defender XDR KQL wherever Defender records the activity, and the YARA and Suricata. Three days of it free, no card.
Behavioural rules are generated from public reporting — validate in your environment before deploying.
Source reporting: https://www.ransomware.live/id/U1VVTlRPLkNOKFNVVU5UTy5DT00pQGNsb3A=
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,854 reports from 146 sources, 616 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs