Flo Components was listed on 04 June 2025 by the sarcoma ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). sarcoma listed 16 organizations that month and 144 in total.
- Listed 533 days ago.
- 507 organizations were listed by all groups in June 2025, see the month.
- 81 in Manufacturing that month.
- 23 in CA that month.
- 1 other listing for the same organization.
Updated 2026-11-19 06:09 UTC. Data: public leak-site listings. How we work.
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
- Sarcoma 144 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.
Flo Components FLO Components Ltd. is an automatic greasing systems specialist and has been a leading supplier of “Total Lube Solutions” to major manufacturers since 1977. More recently, FLO has teamed up with AFEX to help FLO customers protect their critical heavy equipment with the only Fire Suppression Systems designed specifically for heavy mobile equipment. With offices in Mississauga, ON and Winnipeg, MB, FLO uses application expertise, qualified installation and service technicians, combined with high-quality products to provide effective Equipment Reliability Solutions for all types of vehicle fire suppression, manual lubrication, central automatic lubrication and fluid handling applications. We design, assemble and install the highest quality automated systems, using components from industry leaders such as AFEX, Graco, SKF, Lincoln, Alemite, Trico, Perma, Oil-Rite, Petro-Canada…
Show the full post (1023 characters)
Flo Components FLO Components Ltd. is an automatic greasing systems specialist and has been a leading supplier of “Total Lube Solutions” to major manufacturers since 1977. More recently, FLO has teamed up with AFEX to help FLO customers protect their critical heavy equipment with the only Fire Suppression Systems designed specifically for heavy mobile equipment. With offices in Mississauga, ON and Winnipeg, MB, FLO uses application expertise, qualified installation and service technicians, combined with high-quality products to provide effective Equipment Reliability Solutions for all types of vehicle fire suppression, manual lubrication, central automatic lubrication and fluid handling applications. We design, assemble and install the highest quality automated systems, using components from industry leaders such as AFEX, Graco, SKF, Lincoln, Alemite, Trico, Perma, Oil-Rite, Petro-Canada, Lubcon, Super Lube, Anderol and other world-class manufacturers.Geo: Canada - Leak size: 172 GB Archive - Contains: Files
Amounts as written
- 172 GB
Plain-English summary AI-written
The group says it holds information about FLO Components, including its equipment reliability, lubrication, fire suppression, and fluid handling services.
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 Flo Components (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 Flo Components 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 Flo Components 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 Flo Components 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 Flo Components
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: 172 GB. Treat group figures as unverified.
- Lock down exposed admin, VPN and SSO panels Restrict by IP allow-list or a zero-trust proxy and require MFA. Why: A passive scan found 1 critical panel(s) reachable from the internet.
- 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
Listing severity score (heuristic)
60/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 IntelligenceRun a free passive scan on your own domain to see what an attacker can see from the outside.