World Cup 2034 was listed on 03 October 2026 by the Wallstreet ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). Wallstreet listed 22 organizations that month and 48 in total.
- Listed 48 days ago.
- 1147 organizations were listed by all groups in October 2026, see the month.
- 62 in Financial Services that month.
- 3 in SA that month.
Updated 2026-11-19 05:33 UTC. Data: public leak-site listings. How we work.
World Cup 2034
Threat Group Post & Evidence
- Listed by
- Wallstreet 48 listings in total
- Data size the group claims
- 17 TB
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.
We compromised the network of the China Railway Construction Corporation Saudi Branch / Sama Construction consortium, the MAIN CONTRACTOR building the Jeddah Central Stadium for the FIFA World Cup 2034. 17 TB / 1.5M files exfiltrated, including: - Main contract documents, interim payment certificates, and claims against the owner (Jeddah Central Development Company, PIF) - Active dispute and suspension claim records - Personal data of 150,000+ employees, incl. Saudi employees - IFC design documentation for the stadium - Supplier and subcontractor commercial data (bid tabulations)
Amounts as written
- 17 TB
- 17 TB
- 1.5M files
- 150,000+ employees
Kinds of data mentioned
-
Employee and HR records
“…Active dispute and suspension claim records - Personal data of 150,000+ employees, incl. Saudi employees - IFC design documentation for the stadium - Supplier and subcontractor…”
-
Contracts and legal files
“…FIFA World Cup 2034. 17 TB / 1.5M files exfiltrated, including: - Main contract documents, interim payment certificates, and claims against the owner (Jeddah Central Development…”
Plain-English summary AI-written
The group says it holds 17 TB of files, including stadium contract and design documents, dispute records, personal data for over 150,000 employees, and supplier and subcontractor commercial 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 World Cup 2034 (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 World Cup 2034 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 World Cup 2034 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: employee and hr records.
Within 30 days
- Keep watching World Cup 2034 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 World Cup 2034
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.
- 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: 17 TB. Treat group figures as unverified.
- Check regulatory and stakeholder notification duties Saudi Arabia: the Personal Data Protection Law sets breach notification duties to the regulator (SDAIA). This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: Saudi Arabia.
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.
- Check shared suppliers and software List the suppliers and software you share with other Financial Services organizations and ask them whether they were affected. Why: Wallstreet listed 1 other Financial 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)
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 IntelligenceNo 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 →Run a free passive scan on your own domain to see what an attacker can see from the outside.