iMatica was listed on 27 June 2023 by the rhysida ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). rhysida listed 19 organizations that month and 328 in total.
- Listed 1241 days ago.
- 399 organizations were listed by all groups in June 2023, see the month.
- 70 in Professional Services that month.
Updated 2026-11-19 06:49 UTC. Data: public leak-site listings. How we work.
Threat Group Post & Evidence
- Listed by
- Rhysida 328 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.
iMatica iMatica was born in 2001 in Girona and we have expanded throughout the peninsula to provide more and better service. The specialty of the house is the implementation of business management software, also called ERP or billing and accounting program. Documents Data Catalog: 717 GB, 568 473 Files 90% Not sold data was uploaded, data hunters, enjoy More
Amounts as written
- 717 GB
- 473 Files
Kinds of data mentioned
-
Accounting and ledgers
“…implementation of business management software, also called ERP or billing and accounting program. Documents Data Catalog: 717 GB, 568 473 Files 90% Not sold data was uploaded, data…”
Plain-English summary AI-written
The group says it has a catalog of documents and other data.
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 iMatica (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 iMatica 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 iMatica 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.
- 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: accounting and ledgers.
Within 30 days
- Keep watching iMatica 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 iMatica
First 24 hours
- 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: accounting and ledgers.
Within 3 days
- 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: 717 GB, 473 Files. 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.
- Retire staging and dev exposure Take non-production hosts off the internet or behind authentication, and rotate any secrets they held. Why: A passive scan found 1 non-production host(s) that are public.
- 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
- Check shared suppliers and software List the suppliers and software you share with other Professional Services organizations and ask them whether they were affected. Why: rhysida listed 13 other Professional Services 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)
58/100 • GUARDEDA 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.