Back to Intelligence

Coles Cybersecurity Incident: Ransomware Defense and Threat Hunting Guide for Retail Environments

SA
Security Arsenal Team
November 16, 2026
9 min read

Coles Group Limited — Australia's second-largest retailer, with a vast attack surface spanning point-of-sale (POS) estates, e-commerce platforms, loyalty programs holding millions of customer records, and a deeply interconnected supply chain — has confirmed it is investigating a "cyber security incident." At the time of reporting, the company states its stores remain operational, which tells experienced responders one of two things: either the intrusion is contained to corporate/IT systems, or the organization is in the critical early hours of discovery before full scoping is complete.

Having led IR engagements for ransomware and supply-chain compromises in retail and logistics environments, I can tell you that "stores not impacted" is a deliberately narrow statement. It says nothing about corporate Active Directory, e-commerce backends, customer data repositories, HR systems, or third-party integrations. Retail organizations are high-value targets precisely because downtime pressure drives ransom payments, and because they aggregate payment data, personally identifiable information (PII), and supplier credentials in one estate.

No CVE has been publicly attributed to this incident at the time of writing, and no threat actor has claimed responsibility. This post therefore focuses on the most probable intrusion patterns we see in retail-sector incidents — credential-based initial access, living-off-the-land lateral movement, and data staging ahead of extortion — and gives your SOC concrete, low-noise detections to hunt for these behaviors today. If you operate in retail, hospitality, logistics, or any business dependent on continuous POS availability, treat this as a threat-hunting trigger, not just a news story.

Technical Analysis

What We Know — and What the Gaps Tell Us

Public reporting on the Coles incident is thin on technical detail, which is normal in the first 24–72 hours of an investigation. The confirmed facts:

  • Victim: Coles Group Limited, one of Australia's "big two" supermarket operators.
  • Status: Under active investigation; characterized as a "cyber security incident" (a term Australian organizations typically use when the event is more than a failed attempt but scoping is incomplete).
  • Impact: Stores reported as unaffected. No confirmation yet of data theft, encryption, or actor attribution.

The phrase "not impacted stores" is a strong signal that the point-of-sale and store operational technology segment may be segregated from whatever was hit — or that the attacker had not yet reached deployment/detonation stage when detected. In our ransomware engagements, the median dwell time between initial access and encryption is measured in days, not hours. Detection before impact is the best possible outcome, and it usually means the attacker was caught during reconnaissance, credential theft, or staging.

Most Probable Attack Chain in Retail Intrusions

Based on current 2025–2026 retail-sector intrusion patterns, defenders should prioritize hunting the following chain:

  1. Initial access — Phishing with credential harvesting, abuse of remote access solutions (VPN/VDI/RMM tools), or compromised third-party credentials. Valid account abuse (MITRE ATT&CK T1078) remains the dominant initial vector in retail breaches.
  2. Discovery and credential access — nltest, net group, AD enumeration, and access to LSASS memory or credential stores.
  3. Lateral movement — RDP, SMB/admin shares, WinRM, or PsExec-style service creation from a small number of "patient zero" hosts.
  4. Staging and exfiltration — Archive creation (7-Zip/WinRAR) on file servers, followed by transfer to attacker-controlled cloud storage (MEGA, file.io, temp hosting) or direct exfil over HTTPS. Double-extortion is now the default: data is stolen before any encryption.
  5. Impact (if not stopped) — Mass encryption, deletion of Volume Shadow Copies, and tampering with backup agents.

Exploitation Status

  • CVE attribution: None published at time of writing. No CVSS score applies.
  • Active exploitation: The incident itself is confirmed; specific TTPs are not yet public.
  • CISA KEV: Not applicable — no CVE has been named.

This is a behavioral hunting scenario: you are detecting techniques, not a signature. That is precisely where Sigma, KQL, and Velociraptor earn their keep.

Detection & Response

The detections below target the techniques most commonly observed in retail ransomware and extortion intrusions — shadow copy deletion, mass archive staging, and suspicious authentication patterns associated with lateral movement. They are tuned to minimize false positives; deploy them, baseline against your environment, and treat any hit as an investigation trigger.

Sigma Rules

YAML
---
title: Volume Shadow Copy Deletion via vssadmin or wmic
id: 9f2b7c41-3e8a-4d1f-b6c2-8a4e5d6f7a8b
status: experimental
description: Detects deletion of Volume Shadow Copies, a hallmark pre-encryption behavior in ransomware intrusions such as those targeting retail enterprises.
references:
  - https://attack.mitre.org/techniques/T1490/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.impact
  - attack.t1490
logsource:
  category: process_creation
  product: windows
detection:
  selection_img:
    Image|endswith:
      - '\vssadmin.exe'
      - '\wmic.exe'
  selection_cmd:
    CommandLine|contains:
      - 'delete shadows'
      - 'shadowcopy delete'
      - 'resize shadowstorage'
  condition: selection_img and selection_cmd
falsepositives:
  - Rare legitimate backup maintenance; verify against change windows and administrator identity
level: high
---
title: Mass Archive Creation on File Servers via Command-Line Archivers
id: 2c4d8e10-5f6a-4b7c-9d1e-3a5b7c9d1e2f
status: experimental
description: Detects 7-Zip, WinRAR, or similar command-line archivers invoked with password or multi-volume flags, consistent with data staging prior to exfiltration in retail breach scenarios.
references:
  - https://attack.mitre.org/techniques/T1560/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.collection
  - attack.t1560.001
logsource:
  category: process_creation
  product: windows
detection:
  selection_img:
    Image|endswith:
      - '\7z.exe'
      - '\7za.exe'
      - '\rar.exe'
      - '\winrar.exe'
  selection_flags:
    CommandLine|contains:
      - ' -p'
      - ' -v'
      - ' a -t7z'
      - ' a -trar'
  condition: selection_img and selection_flags
falsepositives:
  - Legitimate IT archival jobs; correlate with service accounts and scheduled tasks
level: medium
---
title: Suspicious Remote Session from Non-Administrative Workstation Subnet
id: 6e8a1c35-7b9d-4e2f-a4c6-9d1e3f5a7b9c
status: experimental
description: Detects RDP or WinRM process activity originating from unexpected hosts, a common lateral movement indicator in retail intrusions where attackers pivot from a single compromised endpoint.
references:
  - https://attack.mitre.org/techniques/T1021/
author: Security Arsenal
date: 2026/04/06
tags:
  - attack.lateral_movement
  - attack.t1021.001
logsource:
  category: process_creation
  product: windows
detection:
  selection:
    Image|endswith:
      - '\mstsc.exe'
      - '\wsmprovhost.exe'
    CommandLine|contains:
      - '/v:'
      - '-File'
  filter_admin_hosts:
    Computer|startswith:
      - 'ADMIN-WS'
      - 'IT-JUMP'
  condition: selection and not filter_admin_hosts
falsepositives:
  - Helpdesk remote support; tune the filter to your jump-host naming convention before deployment
level: medium

KQL — Microsoft Sentinel / Defender

This query hunts for the convergence of pre-ransomware behaviors: shadow copy deletion, suspicious archiving, and anomalous logon patterns across the estate. It assumes Sysmon/Security event ingestion plus Defender process telemetry.

KQL — Microsoft Sentinel / Defender
// Hunt: Pre-ransomware staging behaviors across the estate
let Lookback = 7d;
let ShadowCopy =
    DeviceProcessEvents
    | where TimeGenerated > ago(Lookback)
    | where FileName in~ ("vssadmin.exe", "wmic.exe")
    | where ProcessCommandLine has_any ("delete shadows", "shadowcopy delete", "resize shadowstorage")
    | project TimeGenerated, DeviceName, AccountName, ProcessCommandLine, InitiatingProcessFileName;
let Archiving =
    DeviceProcessEvents
    | where TimeGenerated > ago(Lookback)
    | where FileName in~ ("7z.exe", "7za.exe", "rar.exe", "winrar.exe")
    | where ProcessCommandLine has_any (" -p", " -v", " a -t")
    | project TimeGenerated, DeviceName, AccountName, ProcessCommandLine;
let AnomalousLogons =
    SecurityEvent
    | where TimeGenerated > ago(Lookback)
    | where EventID == 4624 and LogonType in (3, 10)
    | summarize LogonCount = count(), DistinctTargets = dcount(Computer) by Account, IpAddress
    | where DistinctTargets > 10;
union ShadowCopy, Archiving
| order by TimeGenerated desc;
// Review AnomalousLogons separately: single accounts touching >10 hosts in 7 days warrant triage
AnomalousLogons

Velociraptor VQL

Use this hunt artifact on suspected patient-zero hosts and file servers to surface staging artifacts and suspicious processes in one pass.

VQL — Velociraptor
-- Hunt: ransomware staging indicators - suspicious processes and recently created archives
SELECT Pid, Name, CommandLine, Exe, Username, CreateTime
FROM pslist()
WHERE CommandLine =~ '(?i)(vssadmin.*delete|shadowcopy delete|7z.*-p|rar.*-p)'
   OR Exe =~ '(?i)(7z|winrar|rar)\.exe$'

-- Correlate with recently created large archives in user and server directories
SELECT FullPath, Size, Mtime
FROM glob(globs=['C:/Users/*/**/*.7z', 'C:/Users/*/**/*.rar', 'D:/Shares/**/*.7z'],
          accessor='ntfs')
WHERE Mtime > (now() - 604800) AND Size > 10485760

Remediation / Hardening Script

The following PowerShell verifies that Volume Shadow Copies are protected, confirms SMB signing posture, audits RDP exposure, and checks for suspicious scheduled tasks created in the last 7 days — the quick hygiene sweep we run at the start of every retail IR scoping call.

PowerShell
# Coles-incident-inspired hygiene sweep - run elevated on servers and critical workstations

# 1. Verify Volume Shadow Copy service and existing shadows
Get-Service VSS | Select-Object Name, Status, StartType
vssadmin list shadows

# 2. Audit RDP exposure - should be disabled or restricted on non-admin hosts
Get-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server' -Name fDenyTSConnections
Get-NetFirewallRule -DisplayGroup 'Remote Desktop' | Where-Object Enabled -eq 'True' | Select-Object DisplayName, Profile

# 3. Check SMB signing enforcement (mitigates relay-based lateral movement)
Get-SmbServerConfiguration | Select-Object RequireSecuritySignature, EnableSecuritySignature

# 4. Hunt scheduled tasks created in the last 7 days (common persistence)
Get-ScheduledTask | Where-Object { $_.Date -and ([datetime]$_.Date -gt (Get-Date).AddDays(-7)) } |
  Select-Object TaskName, TaskPath, Author, Date

# 5. Identify processes with command-line archivers running right now
Get-CimInstance Win32_Process |
  Where-Object { $_.Name -match '^(7z|7za|rar|winrar)\.exe$' } |
  Select-Object ProcessId, Name, CommandLine, @{N='User';E={$_.GetOwner().User}}

Remediation

Because no CVE or specific vulnerability has been disclosed in the Coles incident, remediation is posture-driven, not patch-driven. These are the actions that consistently change outcomes in retail intrusions:

  1. Activate your IR retainer and preserve evidence now. If you observe any of the behaviors above, capture volatile data (memory, netstat, process lists) from suspected hosts before remediation wipes it. Australian organizations should engage the Australian Cyber Security Centre (ACSC) early and review obligations under the Notifiable Data Breaches scheme if customer PII may be involved.
  2. Enforce phishing-resistant MFA on all remote access. VPN, VDI, RMM platforms, and third-party support accounts are the top initial-access vectors in retail. Valid-account abuse defeated password-only MFA in most of the intrusions we responded to in the past 18 months.
  3. Segment POS and store networks from corporate IT. Coles' statement that stores are unaffected likely reflects segmentation working as designed. Validate yours: no direct SMB/RDP path from corporate workstations to store controllers, and no shared service accounts across the boundary.
  4. Harden backup and recovery. Immutable/offline backups, restricted access to backup consoles, and alerting on shadow copy deletion (the Sigma rule above) are the difference between a bad week and a business-ending event.
  5. Monitor for data staging, not just encryption. Double extortion means the damaging act — data theft — happens silently days before any ransom note. Alert on command-line archivers, large outbound transfers to consumer cloud storage, and single accounts touching an abnormal number of hosts (the KQL above).
  6. Review third-party and supply-chain access. Retail intrusions increasingly originate through logistics, HVAC, or IT service providers with standing access. Inventory, time-box, and monitor every external connection.
  7. Watch for follow-on fraud. If customer or employee data is confirmed stolen, expect credential-stuffing waves against loyalty and e-commerce accounts, plus highly targeted phishing against staff. Pre-position rate limiting and credential-leak monitoring now.

Monitor the ACSC (cyber.gov.au), Coles Group's official statements, and BleepingComputer's coverage for attribution and technical indicators as the investigation matures — and feed any published IOCs into the hunts above immediately.

Related Resources

Security Arsenal Managed SOC Services AlertMonitor Platform Book a SOC Assessment soc-mdr Intel Hub

Is your security operations ready?

Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.