SteelTech Inc. was listed on 18 November 2026 by the rhysida ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). rhysida listed 15 organizations that month and 328 in total.
- Listed 2 days ago.
- 983 organizations were listed by all groups in November 2026, see the month.
- 142 in Manufacturing that month.
Updated 2026-11-19 05:29 UTC. Data: public leak-site listings. How we work.
SteelTech Inc.
Threat Group Post & Evidence
- Listed by
- Rhysida 328 listings in total
The listing states no data size and no ransom demand.
Dark Web Leak Proof Screenshot
Original Source (Safe Tor Stream)The group's leak-site address is on paid plans
Free accounts see who listed this organization, when, and what the post claims. The address of the group's own page is shown to license-key holders. If you have a key, see what a license key adds.
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.
SteelTech Inc. SteelTech Inc. (doing business as HeatMaster SS), a Canadian outdoor woodfurnace manufacturer from Winkler, Manitoba, has lost all of its servers.1.370.000 files, 1.5 TB - complete Sage 50 accounting booksfor 2023-2027, both management mail archives, the domain controllerdatabase with password hashes of every employee, and the company's entirescan archive.Most sensitive:- Social Insurance Numbers, dates of birth, addresses and phone numbers of 183 employees - in plain text, inside the payroll table.- Bank account details of 55 employees (payroll EFT files).- Complete identity sets of underage workers (birth certificates, Manitoba Health cards, driver licences) - Manitoba Youth Jobs program.- Financial collapse: revenue fell from $26.9M to $17.3M (-36%), operating loss ~$3.1M, chequing account overdrawn by $1.19M, $3.5M owed to lender Roynat Capital.- Dealer complaints abou…
Show the full post (1415 characters)
SteelTech Inc. SteelTech Inc. (doing business as HeatMaster SS), a Canadian outdoor woodfurnace manufacturer from Winkler, Manitoba, has lost all of its servers.1.370.000 files, 1.5 TB - complete Sage 50 accounting booksfor 2023-2027, both management mail archives, the domain controllerdatabase with password hashes of every employee, and the company's entirescan archive.Most sensitive:- Social Insurance Numbers, dates of birth, addresses and phone numbers of 183 employees - in plain text, inside the payroll table.- Bank account details of 55 employees (payroll EFT files).- Complete identity sets of underage workers (birth certificates, Manitoba Health cards, driver licences) - Manitoba Youth Jobs program.- Financial collapse: revenue fell from $26.9M to $17.3M (-36%), operating loss ~$3.1M, chequing account overdrawn by $1.19M, $3.5M owed to lender Roynat Capital.- Dealer complaints about rust on brand-new stoves, refractory cracking, and 14 furnaces with 'missing' serial numbers.- A 2020-2026 archive of workplace injuries, including named investigations and asbestos correspondence.- Passwords to 73 corporate services in a single Excel file.- A failed IRS registration: US customers were promised the 25C tax credit the company could not legally arrange.The company is owned by the founder's sons - Ryan, Derek and DevonFriesen - who bought it from their father with borrowed money. More
Amounts as written
- 1.370.000 files
- 1.5 TB
- 183 employees
- 55 employees
Kinds of data mentioned
-
Tax records
“…correspondence.- Passwords to 73 corporate services in a single Excel file.- A failed IRS registration: US customers were promised the 25C tax credit the company could not legally…”
-
Accounting and ledgers
“…has lost all of its servers.1.370.000 files, 1.5 TB - complete Sage 50 accounting booksfor 2023-2027, both management mail archives, the domain controllerdatabase with password…”
-
Banking and wire details
“…phone numbers of 183 employees - in plain text, inside the payroll table.- Bank account details of 55 employees (payroll EFT files).- Complete identity sets of underage workers (birth…”
-
Payroll and salaries
“…addresses and phone numbers of 183 employees - in plain text, inside the payroll table.- Bank account details of 55 employees (payroll EFT files).- Complete identity sets…”
-
Identity documents
“…employees (payroll EFT files).- Complete identity sets of underage workers (birth certificates, Manitoba Health cards, driver licences) - Manitoba Youth Jobs program.- Financial collapse:…”
-
Passwords and credentials
“…2023-2027, both management mail archives, the domain controllerdatabase with password hashes of every employee, and the company's entirescan archive.Most sensitive:- Social Insurance…”
-
Customer or client data
“…corporate services in a single Excel file.- A failed IRS registration: US customers were promised the 25C tax credit the company could not legally arrange.The company is owned…”
-
Employee and HR records
“…archives, the domain controllerdatabase with password hashes of every employee, and the company's entirescan archive.Most sensitive:- Social Insurance Numbers, dates of…”
Plain-English summary AI-written
The group says it holds company servers and files, accounting books, email archives, employee password hashes, scan archives, personal and banking details for employees, and identity documents for underage workers.
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 SteelTech (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 SteelTech 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 SteelTech 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.
- Expect convincing phishing Messages that quote real orders, invoices or names are more likely after a leak. Tell finance and the help desk to treat any request from, or about, this company with extra care. Why: The post names: customer or client data, passwords and credentials, identity documents, employee and hr records.
- 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, payroll and salaries, accounting and ledgers, tax records.
Within 30 days
- Keep watching SteelTech 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 SteelTech
First 24 hours
- Reset credentials and sessions Force password, API-key and session-token resets for the accounts the post suggests were exposed, enforce phishing-resistant MFA, and revoke OAuth/SSO grants issued before the listing date. Why: The post names: passwords and credentials, identity documents, customer or client data, payroll and salaries.
- 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, payroll and salaries, accounting and ledgers.
Within 3 days
- Support affected individuals Identify the employees or customers whose identity data may be in scope and offer identity-protection or credit monitoring; brief the help desk on likely phishing. Why: The post names: employee and hr records, identity documents.
- Size the exposure against your own systems Inventory which systems hold data of the kind and volume claimed, so notification and legal decisions rest on your records rather than the group's figures. Why: The post claims: 1.370.000 files, 1.5 TB, 183 employees. Treat group figures as unverified.
- Check regulatory and stakeholder notification duties No country is recorded for this listing. Identify the data-protection and contractual duties that apply where the affected people live, and ask counsel. General guidance, not legal advice. Why: The listing records no country.
-
Check the ways rhysida is reported to get in
Check these first; they are how the group is reported to work in general.
- Actors typically log in to VPN access points with stolen valid credentials, which the advisory ties to organizations without multi-factor authentication. (update of Apr 2025)
Within 30 days
- Watch for tax-filing fraud Tell your tax advisers and, where available, tax authorities so fraudulent filings made with exposed identifiers can be caught early. Why: The post names: tax records.
- Check shared suppliers and software List the suppliers and software you share with other Manufacturing organizations and ask them whether they were affected. Why: rhysida listed 5 other Manufacturing 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)
79/100 • ELEVATEDA 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.
Launch Attack Surface Recon →Run a free passive scan on your own domain to see what an attacker can see from the outside.