Saskatoon Tribal Council was listed on 05 October 2026 by the thegentlemen ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). thegentlemen listed 143 organizations that month and 1119 in total.
- Listed 44 days ago.
- 1147 organizations were listed by all groups in October 2026, see the month.
- 31 in Government & Defense that month.
- 27 in CA that month.
- 1 other listing for the same organization.
Updated 2026-11-19 05:33 UTC. Data: public leak-site listings. How we work.
Saskatoon Tribal Council
Named in 2 separate listings
Another listing name this organization: a different group, or the same group months apart. Each is a claim the group published, not a confirmed breach. The same group listing it again within a few months is not counted: that is the same listing sent twice or moved from countdown to published.
Threat Group Post & Evidence
- Listed by
- Thegentlemen 1,119 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.
sktc.sk.ca zoominfo.com/c/saskatoon-tribal-council-inc/215335121 Saskatoon Tribal Council (STC) is a non-profit tribal council founded in 1982 in Saskatoon, Saskatchewan (Treaty 6), uniting 7 First Nations with 14,000+ members. Led by Tribal Chief Mark Arcand (since 2017), STC employs 500–600+ people across 5 corporations (health, housing, urban services, investments, community development). Head-body revenue is $14–17M/year (federal ISC funding being the largest source), while the whole group is estimated at ~$45M. Its biggest asset is a stake in Dakota Dunes Casino & Resort ($70M facility, 620+ slots), with its development arm DDCDC generating a record $10.1M gaming revenue in 2023/24 (+33% YoY) and $75M reinvested into communities over 10 years (5,300+ projects). Key operations: 453+ housing units (1,068 waitlisted applications), an Emergency Wellness Centre (2,501 admissions), 17,460…
Show the full post (1000 characters)
sktc.sk.ca zoominfo.com/c/saskatoon-tribal-council-inc/215335121 Saskatoon Tribal Council (STC) is a non-profit tribal council founded in 1982 in Saskatoon, Saskatchewan (Treaty 6), uniting 7 First Nations with 14,000+ members. Led by Tribal Chief Mark Arcand (since 2017), STC employs 500–600+ people across 5 corporations (health, housing, urban services, investments, community development). Head-body revenue is $14–17M/year (federal ISC funding being the largest source), while the whole group is estimated at ~$45M. Its biggest asset is a stake in Dakota Dunes Casino & Resort ($70M facility, 620+ slots), with its development arm DDCDC generating a record $10.1M gaming revenue in 2023/24 (+33% YoY) and $75M reinvested into communities over 10 years (5,300+ projects). Key operations: 453+ housing units (1,068 waitlisted applications), an Emergency Wellness Centre (2,501 admissions), 17,460 health clients, and employment services placing 276 people in jobs. STC holds Accreditation Canada.
Plain-English summary AI-written
The group says it holds information about Saskatoon Tribal Council, including its member First Nations, leadership, workforce, operations, funding, and assets.
Written by an AI model (openai/gpt-6-luna) from the post above. It can contain mistakes: rely on the quote, not the summary.
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 Saskatoon Tribal Council (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 Saskatoon Tribal Council 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 Saskatoon Tribal Council 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.
Within 30 days
- Keep watching Saskatoon Tribal Council 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 Saskatoon Tribal Council
Within 3 days
- Find out what was actually taken The post names no specific kind of data, so no data-specific steps are shown. Check the group's own post and your logs to learn what is claimed and what is real. Why: The listing text names no data types.
- 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.
Within 30 days
- Check shared suppliers and software List the suppliers and software you share with other Government & Defense organizations and ask them whether they were affected. Why: thegentlemen listed 13 other Government & Defense organization(s) in the last 90 days.
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
Listing severity score (heuristic)
81/100 • CRITICALA heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.
External Attack Surface Profile
ASM IntelligenceNo scan has been run for this domain yet, so there are no figures to show. Running one is passive: it reads public DNS and certificate records only.
Open the full attack surface scan →Run a free passive scan on your own domain to see what an attacker can see from the outside.