MAP SA was listed on 13 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 35 days ago.
- 1147 organizations were listed by all groups in October 2026, see the month.
- 70 in Education that month.
- 12 in CH that month.
Updated 2026-11-14 15:56 UTC. Data: public leak-site listings. How we work.
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.
map.ch MAP SA Swiss communications agency in Cossonay, Vaud (UID CHE-106.859.955), operating since 1968 as a business; the current legal entity was registered in 1981. It's a ~13-person full-service shop covering brand strategy, SEO/SEA, social media, and event management. Leadership: Sébastien Graap (took over 2003) and Caroline Müller (partner since 2008). Only revenue figure ever made public is ~CHF 2M for 2010; no current financials are disclosed anywhere. Core clients are French-speaking Swiss SMEs and public bodies — CarPostal, Transports publics de la région lausannoise, La Source, Yverdon Énergies, Changins. A separate training arm, map.academy, publishes rates (CHF 800–3,900 packages, CHF 1,200/day, CHF 890/month coaching); agency project work is quote-only. Portfolio runs ~30 cases with claimed results (e.g. 7% energy savings, 1,200+ event visitors)
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 MAP SA (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 MAP SA 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 MAP SA 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 MAP SA 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 MAP SA
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 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.
Within 30 days
- Check shared suppliers and software List the suppliers and software you share with other Education organizations and ask them whether they were affected. Why: thegentlemen listed 28 other Education 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 IntelligenceRun a free passive scan on your own domain to see what an attacker can see from the outside.