Threat Intelligence

Kairos Ransomware Hits Gregory Jewellers: 574 GB of Data Extortion at an Australian Luxury Retailer

The Kairos extortion group claims it stole roughly 574 GB from Australian luxury jeweller Gregory Jewellers. Here is what is verified, what the group's playbook tells us, and why pure data-extortion crews are the harder problem.

Nayan Dey
Senior Security Engineer
7 min read

Luxury retail runs on trust. When you hand a jeweller a passport scan to verify a high-value purchase, or you let them keep your purchase history so the salesperson remembers your anniversary, you are extending a quiet form of credit: you assume the data stays where it belongs. In late April 2026, that assumption broke for the customers of Gregory Jewellers, a Sydney-based fine-jewellery retailer with more than four decades of trading history. The extortion group Kairos listed the company on its dark web leak site and claimed to have exfiltrated roughly 574 GB of internal data.

Gregory Jewellers has confirmed it is investigating the incident and assessing the validity of the claims. As of this writing, the company has not confirmed whether customer or employee data was compromised, and the full scope remains under review. That gap between "a group claims X" and "the victim confirms X" is where most of the useful analysis lives, so let us stay disciplined about it.

What is actually confirmed

According to reporting from Cyber Daily and tracking on ransomware.live, Kairos posted Gregory Jewellers to its leak site on or around 22 April 2026 and claimed approximately 574 GB of stolen data. The sample the group shared reportedly included client personal information, internal documents, customer purchase history, and at least one passport image. Shortly after, the listing disappeared from the leak site and the sample became inaccessible.

That last detail matters. A listing that goes dark within days can mean several things: a victim opened negotiations, the group rotated its infrastructure, or the claim was thinner than advertised and got pulled. None of those readings is confirmed, so treat the 574 GB figure as a claim by the attacker, not an audited number. Extortion crews routinely inflate volume because the headline number is itself a pressure tactic. What we can say firmly is that a sample existed and that it appeared to contain genuinely sensitive identity documents.

Who Kairos is, and why "ransomware" is the wrong word

Calling this a "ransomware hit" is convenient shorthand, but it misreads the adversary. Kairos, active since roughly late 2024, is a data-extortion group, not a classic encryption crew. Per profiles from SOCRadar and others, the group generally does not deploy file-encrypting ransomware at all. It steals data and threatens to publish it unless paid.

The operational pattern reported for Kairos is worth internalising because it shapes the defence:

  • They buy access. Kairos is an active customer in Initial Access Broker (IAB) markets, purchasing footholds into networks rather than burning their own zero-days. They shop by criteria: geography, industry, revenue. A 45-year-old Australian luxury retailer with high-net-worth clientele is exactly the profile such a buyer screens for.
  • They use living-off-the-land tooling. Reported tradecraft includes staging and exfiltrating data with RClone, a legitimate file-transfer utility, moving it over SFTP to overseas hosting. Nothing here trips a signature-based antivirus.
  • They apply human pressure, not crypto-lockers. In documented cases, Kairos has emailed staff directly from compromised internal accounts to announce the breach, then run a time-bound escalation: pay to have the data deleted, or watch it leak.

Their victim count reflects a deliberate, mid-tier operation rather than a mass-spray campaign. Public trackers have attributed roughly a dozen victims to the original "Kairos" name and a larger set under a "Kairos V2" banner, concentrated in the United States and skewing toward healthcare, manufacturing, and business services. An Australian retailer is a slight departure from that center of gravity, which fits the broader 2026 trend of extortion crews broadening their geography.

The "buy access, exfiltrate quietly, then pressure people" model also explains why the Gregory Jewellers timeline is so compressed. A group that does not need to develop an exploit, move laterally to a domain controller, and stage an encryption payload can go from foothold to leak-site listing in a fraction of the time a traditional ransomware affiliate would take. Speed is the point. The faster the data is out and the victim is named, the less time a defender has to detect the egress, and the more credible the threat to publish feels when the negotiation email lands.

The May 2026 backdrop: not an outlier

Gregory Jewellers did not get unlucky in a quiet month. The wider data confirms a busy, escalating period. BlackFog's State of Ransomware tracking recorded around 95 publicly disclosed ransomware and extortion attacks in May 2026 across 17 countries, with the United States again leading at 54 and healthcare the hardest-hit sector at 28 attacks. Australia saw a notable uptick. Separately, Check Point's May telemetry described overall cyberattack volume easing slightly while ransomware activity surged on the order of 48 percent, and other monthly roundups counted hundreds of named victims across dozens of active groups.

Read those numbers together and the signal is clear: the encryption-versus-extortion line is dissolving, the number of active brands is not consolidating, and "publicly disclosed" undercounts reality because plenty of victims pay quietly and never appear on a leak site. The Gregory Jewellers listing vanishing within days is, statistically, the normal texture of this market, not an anomaly.

Why pure extortion is the harder defensive problem

There is an uncomfortable truth here for anyone who built a security program around stopping encryption. If the adversary never encrypts anything, half your incident-response muscle memory does not fire. There is no ransom note on every desktop, no mass file-rename event, no obvious moment of detonation. The "attack" is a quiet copy operation using a tool your developers also use legitimately, followed by an email.

That changes the priorities:

  • Detection has to focus on egress, not just endpoints. Large, anomalous outbound transfers to consumer hosting providers and unfamiliar SFTP destinations are the tell. If you are not baselining normal data egress, RClone-over-SFTP looks like nothing.
  • Identity is the perimeter. Because Kairos buys access and operates from compromised internal accounts, the controls that matter most are phishing-resistant MFA, tight session management, and fast revocation. The breach announcement coming from a real internal mailbox is not a quirk; it is the model.
  • Data minimisation is a control, not a compliance checkbox. A retailer that retains years of purchase history and customer passport scans has converted a sales convenience into a 574 GB liability. The most effective mitigation for "they stole the passports" is frequently "we should not still have had the passports."
  • Third parties expand the blast radius. Luxury retail leans on financing partners, CRM platforms, e-commerce providers, and logistics vendors, each holding a slice of the same sensitive customer record. A breach anywhere in that chain reads the same to the customer whose passport leaks.

How Safeguard Helps

Safeguard treats the supply chain and identity surface as one continuous risk graph, which is exactly the shape of a data-extortion incident like this. Our TPRM workflows, vendor scorecards, and vendor policy registry let retailers see which third parties hold which categories of customer data, so a financing or CRM partner's exposure surfaces before it becomes your breach notification. Our Multi-Agent TAOR Deep Think AI engine, with Griffin AI orchestrating verification above any single model, is built to cut the false positives that bury real egress and identity anomalies in the noise, and we measure ourselves on cost-per-verified-finding rather than raw alert counts. The platform is model-agnostic, so you can plug in your own models as components while the reliability stays in the orchestration layer. If your organisation holds sensitive customer data and wants a clearer picture of where it actually lives, reach out.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.