Ransomware Weekly, 8–14 Nov 2026: 504K Indexed Rows in the LR Reed Claim
Indexed 8–14 Nov 2026: 504K rows in the claimed LR Reed source, including 317K with email. Customer impact and copy authenticity are separate questions.
No Breaches Weekly edition accompanies this report. The cases reviewed for it did not meet our posting-evidence requirements. Past editions.
Covers leaks indexed by HaveIBeenRansom between 2026-11-08 00:00 and 2026-11-14 23:59 UTC. Each case shows when it was listed and when its data became searchable. How we pick cases, read records and score attribution: methodology.
Why this case
This edition examines the claimed LR Reed material that became searchable during the reporting window. Its 503,932 indexed records include 316,914 records containing email, making contact-related exposure the main analytical question. The archived listing and the company's published response provide distinct evidence: the former documents what Kairos claimed, while the latter says customer data was unaffected. Neither authenticates the exact indexed copy. This edition covers one case because the other entries lacked adequate posting evidence.
| Metric | LR Reed |
|---|---|
| Listed by | Kairos |
| Date visible on archived posting | 2026-07-22; no time or timezone shown |
| Capture timestamp (UTC) | 2026-09-26 09:02:21 |
| HIBR observation (UTC) | 2026-07-22 20:27:32 |
| Indexed (UTC) | 2026-11-09 12:45:01 |
| Actor-claimed volume | 335 GB; not independently verified |
| Records indexed | 503,932 |
| Records with email | 316,914 (62.89%) |
| Corporate / personal (% of email-bearing records) | 77.84% / 22.16% |
| API association heuristic v2.0 | Insufficient evidence; no score |
| Exact indexed copy | Not authenticated |
Key findings
503,932 indexed records: HIBR made this source searchable on 9 November. This is an indexing event, not evidence of a new intrusion that week.
316,914 email-bearing records: the contact subset merits scrutiny, but it does not count unique people, customers or compromised accounts.
335 GB claimed by Kairos: the archived posting records that allegation. It does not verify the volume or establish that HIBR indexed all of it.
The original posting capture is retained internally with its provenance and hash. Its visible date has no time or timezone; the capture timestamp and HIBR observation are recorded separately. No leaked records were opened for this review. File-format counters can overlap, and the corporate-classified bucket is not an employee count.
1 · LR Reed (listed by Kairos)
HIBR entry: LR Reed on HaveIBeenRansom
What happened. The archived Kairos listing names LR Reed, displays 22 July 2026 and claims 335 GB. The capture is dated 26 September, after the posting and before HIBR indexed the material on 9 November. The claimed volume is not a verified measurement of the indexed copy. Cyber Daily reported on 23 July that LR Reed was investigating the claims, had notified Australian authorities and said customer data was unaffected because it was stored separately. This response does not authenticate the copy now indexed. We retain the case as claimed and do not describe customers as confirmed victims.
Scale. HIBR reports 503,932 indexed records, of which 316,914 (62.89%) contain email. These are indexed rows, not unique people, accounts or compromised systems. The leading format counters are DATABASES 257,203, CSV 184,329, XLS 132,583. Format counters may overlap; they are not additive or file counts. Rounded for display: 504K records.
What the data contains. The aggregate includes database, CSV, spreadsheet and email-format counters. It supports a description of mixed indexed formats, without showing what any particular message or document contains. No individual names, building details, account records or document images were inspected. The absence of identity-document detections in this metadata cannot establish that the broader source lacks sensitive documents. The indexed material and the scope described in the company's July response must be kept distinct.
Corporate vs Personal. Email appears in 62.89% of the indexed records. Its table includes lrreed.com.au and lrreedcity.com.au alongside other domains. The leading corporate-classified domain is vbcs.com.au; that fact alone establishes neither ownership nor a relationship. The bucket also includes bigpond.com, demonstrating why the API category must not be described as a count of employees. Every percentage below has an explicit record-based denominator.
Email-bearing records, not customers or employees. The corporate category includes ISP domains; the company said customer data was unaffected. Source: HIBR entry.
Corporate-classified: 246,681 (77.84%); personal-provider: 70,233 (22.16%). Denominator: 316,914 email-bearing records, not distinct addresses or people. Each top-domain table uses its own bucket as denominator.
| Corporate-classified domain | % of its bucket |
|---|---|
| vbcs.com.au | 20.49% |
| lrreed.com.au | 10.86% |
| bigpond.com | 4.38% |
| lrreedcity.com.au | 3.73% |
| smartercommunities.com.au | 1.53% |
| Personal-provider domain | % of its bucket |
|---|---|
| gmail.com | 64.90% |
| hotmail.com | 18.53% |
| yahoo.com | 2.70% |
| icloud.com | 2.61% |
| outlook.com | 2.29% |
Attribution confidence: Insufficient evidence. The score is missing; it is not a zero-percent result. The API has no organisation domains configured and evaluates none of the available points. It therefore cannot quantify the link, even though the aggregate domain table contains potentially relevant labels. Hypothesis, not fact: if authentic, this email-bearing material is likely to be useful for contact-led impersonation (low confidence). This assessment concerns the indexed material; it does not contradict the company's statement about customer data or establish any subsequent misuse.
Why it stands out this week. The substantial email-bearing subset warrants attention alongside the company's published response. Readers can act on suspicious communications without accepting the group's account of who was affected. A later statement addressing the exact indexed copy, or an independently verified relationship between that copy and the reported incident, would provide evidence the current score lacks.
What the evidence supports
- The archived posting and independent reporting establish that a Kairos claim about LR Reed existed. They do not establish an initial-access technique, encryption event or present access.
- The missing association score cannot resolve whether this exact indexed copy belongs to LR Reed. A domain in an aggregate table is an investigation lead, not proof of ownership or another organisation's compromise.
- The company's response must accompany any account of the claim. A substantial contact subset does not overturn its statement that customer data was unaffected.
What defenders can do
For LR Reed relationships, preserve the company's statement about customer data in incident notes and communications. If suspicious messages arrive, retain their headers and verify the sender through known contact details; do not turn a contact-domain match into a customer-impact notice.
For the accounts supporting these workflows, CISA recommends phishing-resistant MFA. This is preventive guidance, not an attribution of phishing to this case. No case-specific malware indicator, exploited vulnerability or ATT&CK intrusion sequence is established by the evidence collected here.
Is your company — or one of your suppliers — in a ransomware leak? Search HaveIBeenRansom for free · Monitor your domains with HIBR for business
DarkEye Threat Research · Data: HaveIBeenRansom · Indexing methodology peer-reviewed in MDPI Electronics · Attribution confidence is a heuristic estimate (method v2.0), not a formal attribution.
Spotted an error, or represent an organisation named here? Send us a correction and we will add it to the post.
Darkeye Research Team
JuanmaTracking ransomware crews, breach disclosures and the tooling that matters — field notes from the Darkeye desk.
Intel briefing
Get breach reports before they trend
Ransomware intel and breach disclosures in your inbox. Signal only, no noise.
Read next //
Ransomware Weekly, 1–7 Nov 2026: 53.7M Claimed Henry Pratt Rows, Atomberg and Kirkland & Ellis
Claims indexed 1–7 Nov 2026: Henry Pratt (53.7M rows), Atomberg (8.2M) and Kirkland & Ellis (452K), with domain evidence and attribution limits.
Keep investigating //
Discussion (0)
Sign in to join the discussion
Share your take with the Darkeye community.
No comments yet. Be the first to weigh in.