Ransomware Tracker by ExposureDrift
Dashboard / Victims / Flexmaster

Flexmaster was listed on 07 September 2026 by the Storm ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). Storm listed 37 organizations that month and 88 in total.

  • Listed 73 days ago.
  • 874 organizations were listed by all groups in September 2026, see the month.
  • 158 in Manufacturing that month.
  • 29 in CA that month.

Updated 2026-11-19 05:35 UTC. Data: public leak-site listings. How we work.

Flexmaster corporate emblem
Listed by Storm Disclosed: 2026-09-09 10:11 UTC

Flexmaster

Manufacturing CA

Threat Group Post & Evidence

Listed by
Storm 88 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.

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.

Flexmaster, part of the Novaflex Group, specializes in a wide range of flexible ducting solutions including aluminum, stainless steel, and fabric ducting. Their product offerings also include innovative systems like the Platinum Flow gasketed duct and fume vent solutions. The company caters to various clients in the HVAC industry, providing essential accessories and insulation products. Flexmaster is committed to delivering high-quality, reliable ducting systems for diverse applications. The company headquarters is located in 20 East Pearce Street, Richmond Hill, ON L4B 1B7, Canada. 201-500 Employees

Amounts as written

  • 500 Employees

Plain-English summary AI-written

The group says nothing specific about data it holds.

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 Flexmaster (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 Flexmaster 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 Flexmaster 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 Flexmaster 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 Flexmaster

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.
  • 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: 500 Employees. Treat group figures as unverified.
  • 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 Manufacturing organizations and ask them whether they were affected. Why: Storm listed 12 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

Resolved Domain Not stated
Industry Vertical Manufacturing
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
Industrial manufacturing
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

No 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 →
Is Your Organization Exposed?

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

More Claims by Storm

All →
Baltimore Tank Lines
Transportation 2026-10-19 06:55 UTC
Merit Financial Group
Financial Services 2026-10-19 06:55 UTC
Patriot Maritime
Transportation 2026-10-19 06:54 UTC
R. A. Wood Associates
Professional Services 2026-10-16 09:18 UTC
Tech Electronics
Technology 2026-10-16 09:17 UTC