Ransomware Tracker by ExposureDrift
Dashboard / Victims / Klue.com

Klue.com was listed on 19 June 2026 by the Icarus ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). Icarus listed 11 organizations that month and 12 in total.

  • Listed 152 days ago.
  • 708 organizations were listed by all groups in June 2026, see the month.
  • 104 in Technology that month.
  • 20 in CA that month.

Updated 2026-11-18 11:12 UTC. Data: public leak-site listings. How we work.

Klue.com corporate emblem
Listed by Icarus Disclosed: 2026-06-19 10:50 UTC

Klue.com

klue.com Technology CA

Threat Group Post & Evidence

Listed by
Icarus 12 listings in total

The listing states no data size and no ransom demand.

No capture of the original post

We only show a screenshot when we captured the group's own page ourselves. For this listing we have not, so none is shown.

What the group says it holds

Taken from the group's own post. Ransomware Tracker by ExposureDrift has not seen the data and cannot confirm any of this.

As you've probably already heard, ***.com has been impacted by us recently. A number of other companies' Salesforce instances, which were partners to Klue, were exfiltrated. This leak/post is made to address this. We advice Klue to contact us for a swift resolution, in order not to affect the companies you work with. On the other note, if Klue doesnt want to accommodate this request, we advice the companies who want to protect their data to contact us via Session. In order to verify you're a representative of the company you claim to be, you will need to provide a certain value/field from a row on your SF. We wish for your cooperation, not your demise. Make the correct choice. Data stolen: data borrowed - not stolen

Kinds of data mentioned

  • Banking and wire details

    “…leak/post is made to address this. We advice Klue to contact us for a swift resolution, in order not to affect the companies you work with. On the other note, if Klue…”

What to do about this listing

Choose who you are. Each step shows why it appears and, where we have one, its source. General guidance, not legal or incident-response advice.

If you work with Klue.com (customer, supplier or partner)

Within 3 days

  • Do not open the group's page or download the data Do not visit the leak site or download files from a listing. Holding stolen data can be unlawful, and the files can carry malware. Wait for the company's own notice. Why: A safety rule for any leak listing.
  • Ask Klue.com directly Write to your contact and ask whether your data, or your access to their systems, is in scope, and ask for a written statement. Your contract or data-protection law may oblige them to tell you if your data is affected: check the notification clause. Why: A listing is only the group's claim; the company is the one who can confirm what was taken.
  • Review what Klue.com can reach of yours List the accounts, API keys, VPN or SSO connections and shared mailboxes this company has with you. Rotate the keys you gave them and remove access they do not need. Why: Access a supplier holds is how a listing about them can become a problem for you.
  • Verify payment-detail changes by phone Confirm any change to bank details or any urgent invoice with a number you already hold, not one in the message. Why: The post names: banking and wire details.

Within 30 days

  • Keep watching Klue.com A supplier's listing can change after the first sighting: the group can add data, change the status or publish. Add the company to your supplier list to be told, and check your own domain too. Why: A listing is a moving claim, not a single event. Add to your supplier list Check your own domain
If you are Klue.com

First 24 hours

  • Protect payments Tell your bank, verify any change to supplier or payroll bank details by calling a known number, and watch for invoice-fraud emails that use real names and amounts. Why: The post names: banking and wire details.

Within 3 days

  • Retire staging and dev exposure Take non-production hosts off the internet or behind authentication, and rotate any secrets they held. Why: A passive scan found 2 non-production host(s) that are public.
  • Check regulatory and stakeholder notification duties Canada: PIPEDA requires reporting breaches that pose a real risk of significant harm, as soon as feasible. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: Canada.
General readiness for any ransomware claim (not about this listing)
  • Offline, immutable backups and a restore drill Keep backups outside domain-admin reach and practise a restore; a leak does not remove the risk of re-encryption. Why: General practice for any ransomware claim; not specific to this listing.
  • Look for mass file access and unusual outbound transfers Review EDR, proxy and identity logs for bulk reads, archive creation and large uploads to file-sharing services. Why: General practice for any ransomware claim; not specific to this listing.
  • Phishing-resistant MFA on remote access Enforce MFA on VPN, SSO and admin panels, and retire password-only or SMS-based remote access. Why: General practice for any ransomware claim; not specific to this listing.

Listing details

Resolved Domain klue.com
Industry Vertical Technology
Country CA
Enrichment Status ENRICHED

Listing severity score (heuristic)

50/100 • GUARDED

A heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.

1. Sector Criticality 20/30 pts
Technology and communications
2. Group tier 10/25 pts
Tier 3: all other groups
3. Data Volume & PII Scope 10/25 pts
Baseline: no size or sensitive data named in the post
Formula: sector • group tier • data claimed (scaled to 100) Rule-based score

External Attack Surface Profile

ASM Intelligence
80/100 • CRITICAL
Last Audited: 2026-11-14 16:31 UTC Passive Recon
Total Network Assets 8
6 hosts • 2 unique IPs
0 cloud-hosted • 5 SaaS
Subdomain Assets 6
Critical Panels 0 (VPN/Admin/SSO)
Non-Prod / UAT 2 Staging/Dev
SaaS Ecosystem 5 Cloud Apps
Primary CSP Public Cloud / E
Email Security Grade A (SPF/DMARC)
Open the full attack surface scan →
Is Your Organization Exposed?

Run a free passive scan on your own domain to see what an attacker can see from the outside.

Defense Telemetry

Passive DNS
Mail Gateway Google Workspace
DNS Authority Cloudflare Managed DNS
Edge CDN / Shield Cloudflare CDN / DDoS Shield
SPF Record Configured
DMARC Policy Enforced
Public DNS records only • no port scanning

More Claims by Icarus

All →
H*
Technology 2026-06-23 11:21 UTC
H**
Technology 2026-06-23 11:20 UTC
G*
Technology 2026-06-23 11:20 UTC
C*
Technology 2026-06-23 11:20 UTC
Huntress
Technology 2026-06-22 21:21 UTC
HDS (Hdscorp)
Technology 2026-06-22 21:21 UTC