Yateem Group was listed on 24 April 2023 by the blacknevas ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach).
- Listed 1306 days ago.
- 478 organizations were listed by all groups in April 2023, see the month.
- 48 in Retail & E-Commerce that month.
- 1 other listing for the same organization.
Updated 2026-11-19 05:58 UTC. Data: public leak-site listings. How we work.
Yateem Group
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
- Blacknevas 47 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.
500+ gigabytes and over 100,000+ files availableThe Yateem Group owns nearly 100 optical outlets in addition to many other brands and facilities. At its heart, the group retains the original family values set forth by the founders.A complete customer database with all contacts has been downloaded, including phones and emails of more than 9000000+ records, as well as all internal information on YateemGroup employees, passports, rights, work contracts and insurance.The IT department is aware of the leak, but has broken off negotiations, and customer and employee data is being prepared for publication.(ready to sell all databases without publishing)access was obtained thanks to the IT departments of these companies:Trojan Construction & Holding Group www.trojan.aeT. Choithram And Sons, LLC www.choithrams.com
Amounts as written
- 500+ gigabytes
- 100,000+ files
- 9000000+ records
Kinds of data mentioned
-
Identity documents
“…records, as well as all internal information on YateemGroup employees, passports, rights, work contracts and insurance.The IT department is aware of the leak, but has broken…”
-
Email and communications
“…customer database with all contacts has been downloaded, including phones and emails of more than 9000000+ records, as well as all internal information on YateemGroup employees,…”
-
Customer or client data
“…retains the original family values set forth by the founders.A complete customer database with all contacts has been downloaded, including phones and emails of more than 9000000+…”
-
Employee and HR records
“…than 9000000+ records, as well as all internal information on YateemGroup employees, passports, rights, work contracts and insurance.The IT department is aware of the leak, but…”
-
Contracts and legal files
“…internal information on YateemGroup employees, passports, rights, work contracts and insurance.The IT department is aware of the leak, but has broken off negotiations, and…”
-
Databases and backups
“…the original family values set forth by the founders.A complete customer database with all contacts has been downloaded, including phones and emails of more than 9000000+ records,…”
Plain-English summary AI-written
The group says it holds over 500 gigabytes and 100,000 files, including customer contact records and internal employee information such as passports, work contracts, and insurance details.
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 Yateem Group (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 Yateem Group 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 Yateem Group 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, email and communications, identity documents, employee and hr records.
- Check software and integrations you take from them If you run their software or call their API, check that updates come through the usual channel and rotate the keys and tokens you hold for it. Why: The post names: databases and backups.
Within 30 days
- Keep watching Yateem Group 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 Yateem Group
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: identity documents, email and communications, customer or client data.
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.
- Rotate database and cloud access Rotate database and cloud-storage keys, review public bucket and snapshot sharing, turn on object-level audit logging and keep backup encryption keys separate. Why: The post names: databases and backups.
- Check for mailbox compromise Audit mailbox rules, forwarding and delegated access, rotate mail-admin credentials and move DMARC to p=reject to limit follow-on phishing. Why: The post names: email and communications.
- 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+ gigabytes, 100,000+ files, 9000000+ records. 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.
Within 30 days
- Review privileged and contract material Ask counsel which contracts and privileged files are named, and whether client or partner confidentiality terms oblige you to tell them. Why: The post names: contracts and legal files.
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)
56/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.