Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore
All country reports
Country reportBrandefense Country Report · United Arab Emirates 2026TLP:CLEAR81 min read

Brandefense United Arab Emirates Cyber Threat Landscape Report 2026

Identity exposure, a residents' account market and crisis-period destructive claims in a highly digitised Gulf economy

By
Odin by Brandefense
Published
21 November 2026
Reading time
81 min read
Edition
Version 1.0 · Public Research Edition · TLP:CLEAR
Research window
1 January-20 November 2026

Get the full report.

Free PDF. Fill in the form and the download opens here.

By submitting this form, you agree to our Privacy Policy.

النسخة العربية
109 of 250
organisations had a credential listed for sale on the day of the check
130,477
posts tagged as concerning the UAE, 1 January-20 November 2026
10
DDoS claims in the actor posts we read against UAE targets, all between 2 March and 8 April
12 of 23
banks in our list with a credential listed for sale on the day of the check

Version 1.0 · Public Research Edition · TLP:CLEAR · Brandefense Country Report · United Arab Emirates 2026

About this editionPrepared by Odin by Brandefense from Brandefense Blackhole, Ransompedia and Atlas data. Analysis and first drafts by AI agents (Anthropic Claude); findings reviewed by Brandefense analysts before release. Method summary in Appendix A.

Chapter 1

Executive summary

This chapter answers

What happened in 2026, what matters most for UAE organisations, and what should leaders decide first?

4decisions for leaders, each tied to evidence in the chapters

In short

For the 250 leading UAE organisations we assessed, the main measured exposure is identity: infected-device and credential associations, and credentials listed for sale at 109 of them. The underground trades UAE residents' verified accounts and real-estate data all year. Destructive and DDoS claims against state, energy and transport targets clustered in March and April, and the named bodies did not confirm them. Act in this order: validate listings, test backup restores, then harden account opening.

This report combines three of Brandefense's own data sources with verified public reporting. Brandefense Blackhole supplied 130,477 posts tagged as concerning the UAE and 1,271 distinct forum posts mentioning the UAE. It also supplied infected-device and credential records for 250 selected organisations, and card material that appeared in clear text in posts. Ransompedia supplied ransomware leak-site listings for the UAE and four Gulf comparators. Atlas exposure ratings were computed for the 250 organisations. These are separate populations and are never added together.

1. Credential and infected-device associations touch almost every leading organisation. 234 of the 250 organisations have infected devices associated with their domains (at least 522,128 in total). Most (491,713) are not employee-classified, and many are probably residents' and customers' own devices, though ownership is not established; 30,415 are employee-classified. 241 have historical credential records (1,856,314 records). These counts are all records held on 21 November 2026, whatever their capture date: they are cumulative, not 2026-only. They can involve staff, students, residents or customers. These are association counts: whether any login is still usable, and whose it is, requires validation. [S2][S3]

2. 109 of 250 organisations had a credential listed for sale when checked. Atlas gives the 250 organisations a national headline rating of 53 on a 0-100 scale, where 0 means no risk observed; it is a summary rating, not an average. A listing tells a defender to look for an active account; it does not say how many accounts or whose. [S3]

3. Destructive and DDoS claims clustered during the crisis and remained unconfirmed. Hacktivist DDoS claims in the actor posts we read against federal and emirate websites fell between 2 March and 8 April. Handala, a brand Security Affairs describes as widely seen as a front for an Iran-backed actor, claimed wiper attacks and data theft at several public-sector bodies in one emirate. Its claimed volumes were 6 PB destroyed and 149 TB stolen. Neither the named bodies nor the authorities confirmed these claims by our cut-off. The national cybersecurity authority itself warned of an active regional wiper campaign in April. [S1][S11][S26]

4. Residents' accounts and property data led UAE offers; ransomware listings outpaced Gulf comparators. The most persistent UAE-specific thread is trade in bank, wallet, remittance and exchange accounts tied to an Emirates ID or residence card, and in mule recruitment. Real-estate owner, tenant and portal data was the most frequently advertised UAE-specific dataset category in the reviewed posts, from at least nine sellers. Ransompedia lists 84 UAE ransomware listings in the window, far above Saudi Arabia (30), Qatar (9), Oman (9) and Kuwait (7). [S1][S5]

5. Few incidents in the reviewed public reporting had detailed confirmation. The head of the UAE Cybersecurity Council described a hacker who exploited an unpatched vulnerability at a private-sector organisation and demanded 5 million USD. In November Landmark Group confirmed unauthorised access to its Shukran loyalty programme in which names, contact details and birth dates may have been exposed, a day after a leak-site group listed the company. Separately, vendors reported state-linked espionage against UAE entities through hijacked mailboxes and job lures. [S17][S67][S24][S31][S32]

Four decisions for leaders

  1. Treat current credential listings as an incident trigger, not a statistic. Route every current market listing tied to your domains to the identity team. Contain privileged, remote-access or no-MFA (multi-factor authentication) accounts the same day, and record a disposition for the rest within 5 working days. Arrange monitoring of credential listings and infected devices for your domains from day 1, through an internal team or a provider (§12.1 rows 1-2).
  2. Prove you can recover from a wiper. The Council's own advisory describes destructive malware entering through phishing, stolen VPN credentials and unpatched systems. Restore a critical system from offline backup within the promised time, and patch or isolate end-of-life edge systems (§6.4; §12.1 rows 4 and 6).
  3. Prepare for claims that outrun the facts. Agree in advance who confirms service status publicly during a hacktivist campaign, and pre-arrange upstream DDoS mitigation for public portals before the next heightened period (§12.1 rows 9 and 16).
  4. Break the account-fraud chain. Residence-card KYC, mule accounts and remote-access takeover are one chain. Move approvals off SMS codes and test account opening and recovery with synthetic cases (§8, §10.3; §12.1 rows 10 and 18).

The year in numbers

130,477

Blackhole posts tagged as concerning the UAE, 1 Jan-20 Nov 2026

What it is notNot a count of attacks; October alone holds 32,435, mostly one account-trading bot family

23,663-24,456

relevant posts in January-July and November, given as a range (of 65,544 tagged)

What it is notNot unique incidents; of 30 random relevant posts, only 10 named the UAE specifically

250

leading public and private organisations assessed with Atlas methodology

What it is notNot a random sample; not a national prevalence estimate

522,128+

infected devices associated with those 250 domains (30,415 employee-classified); cumulative, all records held on 21 Nov 2026

What it is notNot 2026-only, not unique people, not verified current infections; a lower bound

109 of 250

organisations with a credential listed for sale at the time of the check

What it is notNot a count of accounts or of confirmed breaches

84

Ransompedia accepted ransomware listings for the UAE dated 1 Jan-20 Nov 2026 (74 distinct plausible UAE organisations)

What it is notNot confirmed intrusions; listings are criminal claims

128

incidents the national cybersecurity authority counted as confirmed by 18 February 2026

What it is notNot comparable with our counts; a different population and method

10

hacktivist DDoS claims in the actor posts we read, all between 2 March and 8 April

What it is notNot confirmed outages

631

distinct UAE-associated payment cards seen in clear text in collected dark-web posts (504 attributed to a named UAE issuer)

What it is notNot a fraud-loss figure; narrow scope (§8.2)

82%

of the 250 organisations enforcing DMARC (204)

What it is notNot a measure of phishing success

Report map

Twelve chapters, five reader paths. Start with the row that matches your role; each chapter opens with the question it answers, and chapters 2-12 close with three takeaways.

Board and executives

What happened, how exposed are we, and what should we decide?

Go to1312

CISO and security leads

Which exposures are ours, which actors matter, and which controls come first?

Go to36791012

SOC and threat intelligence

What did the actors post, how are they connected, and which techniques did espionage use?

Go to467812App. A-B

Fraud and customer protection

How are UAE identities, accounts and cards traded, and where do banks see it?

Go to4589

Communications and legal

How do we speak about unverified claims, and which notification rules apply?

Go to61012

Chapter 2

The United Arab Emirates' digital and threat context

This chapter answers

Which features of the UAE shape its cyber threat picture in 2026, and what did the national authorities report?

99%internet penetration (the source's cap), with 23.0 million cellular connections

In short

Three features shape the UAE's threat picture: near-universal, mobile-first connectivity; a centralised digital-identity model; and a regional crisis from late February, which the national cybersecurity authority linked to a sharp rise in attack attempts. Official figures describe pressure, not outcomes. Plan for destructive malware and identity fraud at once: test offline backups and harden account recovery.

2.1 A connected, mobile-first population

DataReportal counted 11.4 million inhabitants in October 2025 and 11.3 million internet users at the end of 2025, a penetration of 99.0% (DataReportal caps adoption at 99%). It counted 23.0 million cellular connections, 202% of the population, and 12.5 million social-media user identities, which may not be unique people [S8].

Two consequences follow for defenders. Fraud aimed at UAE residents arrives in many languages: the criminal posts we hold about the UAE are mostly in English and Russian, with Arabic a small share (Chapter 4). Mobile numbers, messaging apps and app-based banking are also the main channels for both service delivery and fraud.

2.2 Centralised digital identity and government

The UAE runs a single national digital identity, UAE PASS, which the state news agency WAM reported had more than 12 million registered users [S55]. Federal and emirate-level portals sit behind it. Centralised identity makes services faster and also concentrates value: a working UAE PASS session or a copy of an identity document opens many doors. In March, Dubai Police warned of callers posing as crisis-management staff to obtain UAE PASS and Emirates ID details for SIM-swap and banking-app takeover [S49].

The UAE Cybersecurity Council, set up by Cabinet decision in November 2020 [S54], leads national cyber policy. The Cabinet approved the current National Cybersecurity Strategy on 3 February 2025, built on five pillars: governance, protection, innovation, building capability and partnership [S43]. In June 2026 a new Federal Authority for Artificial Intelligence and Data was announced, which, according to a law-firm analysis, consolidates AI oversight, digital government and data regulation [S41]. Chapter 10 sets out what this means for organisations.

2.3 A regional crisis and the official attack figures

The Council's head reported a heightened period of cyber activity from 28 February to early April 2026, during what he called a regional crisis [S22]. In early March, Amazon's cloud division reported a fire at a UAE data centre after objects struck the facility, which affected service availability; that outage was physical, not a cyberattack. Some online and phone banking services were unavailable the same day, with the cause publicly unknown [S29].

The Council published figures throughout the year. They come from different events, periods and wording, and the Council did not publish a method, so they are not a time series. On 21 October the Council itself stressed that more detected attempts "does not necessarily indicate" more successful breaches [S20].

DateWhat the Council saidSource
2026-02-18128 confirmed incidents since 1 January; 90,000-200,000 breach attempts a day[S9]
2026-02-21Organised attacks "of a terrorist nature" on national platforms thwarted: network intrusion, ransomware and phishing attempts[S10]
2026-04-01Daily attacks up from about 200,000 to about 600,000[S13]
2026-04-20About 800,000 attacks a day during the truce, against about 200,000 before the crisis[S14]
2026-07-03More than 800,000 attempts a day; attacks on financial-sector entities thwarted[S15]
2026-08-10Advanced and organised attacks on aviation, energy and education countered[S16]
2026-09-15640,000 attacks recorded in a single day[S17]
2026-10-21Nearly 750,000 attempts thwarted "in recent months"[S20]
2026-10-28National teams remediated a widespread PHP vulnerability; no CVE was given[S21]
2026-11-18More than 40 groups from over 20 countries tried to exploit the crisis[S22]

The February breakdown is the most useful official baseline. Of the 128 confirmed incidents, the Council classed 38.3% as defacement, 25.8% as data leaks, 13.3% as data breaches, 10.2% as initial access, 7.8% as ransomware and 4.7% as DDoS. Telegram carried 49.2% of the related activity, the open web 40.6% and Tor sites 10.2%. Government (9.4%) and financial services (9.3%) were the most affected sectors [S9]. Telegram also dominates our own collection (99.6% of tagged posts); otherwise the official mix and our post families measure different things and are not compared.

2.4 Official attribution statements

Official statements about who was behind the activity varied by occasion. We record them as reported, without our own attribution.

DateStatement as reportedSource
2026-02-18The Council said "a significant proportion" of attacks were carried out by state-sponsored advanced threat groups. 15 of the 21 tracked APT groups were state-sponsored. The Council also tracked 60 hacktivist and criminal actors[S9]
2026-04-20The Council's head listed groups including, as reported, groups with links to Iran[S14]
2026-09-16In a CNN interview reported by The National, the Council's head named Iran and the IRGC (Islamic Revolutionary Guard Corps)[S18]
2026-09-17Euronews wrote that the same official did not attribute the operations to any state[S19]
2026-11-18At the World Police Summit, the Council's head named Iran and networks linked to the Revolutionary Guard among more than 40 organisations[S23]

What this means for defenders. The attribution debate does not change the controls. The Council's own warnings describe destructive wiper malware, phishing, stolen VPN credentials and unpatched internet-facing systems as the entry points [S11]. Those are the same controls whoever the operator is.

Key takeaways

  1. 01

    Near-universal connectivity and a central digital identity make identity data and sessions the prize.

  2. 02

    Official attack figures measure attempts on different bases; read them as pressure, not as a trend.

  3. 03

    The Council's own advisories name the entry points: phishing, VPN credentials and unpatched edge systems.

Chapter 3

National exposure: 250 leading organisations

This chapter answers

How exposed are the UAE's 250 leading public and private organisations when they are scored the way Brandefense Atlas scores a customer, and which signal should a defender triage first?

109 of 250organisations had a credential listed for sale on the day of the check

In short

We assessed 250 leading UAE organisations using Brandefense Atlas exposure ratings. Almost all have infected devices and credential records associated with their domains, and 109 had a credential listed for sale when we checked. Email hygiene is comparatively strong: 204 of 250 enforce DMARC. DNSSEC is rare. Triage current listings first, then employee devices, then large credential stores at universities and government bodies.

3.1 Universe card

ItemDefinition
Population250 organisations: 68 government bodies, 35 banking and finance, 19 energy and utilities, 19 transport and logistics, 18 education, 16 retail and holdings, 11 insurance, 11 technology, 11 healthcare, 10 real estate and construction, 9 manufacturing and industry, 9 hospitality and tourism, 8 media and 6 telecom. 184 state or state-linked, 60 private, 6 foreign
SelectionPurposive: federal and emirate bodies and portals, central-bank-licensed banks and payment firms, state-linked enterprises and market leaders. Selected for size or systemic role, not ranked by revenue; no published UAE top-250 ranking was used
UnitOne primary domain per organisation. All 250 resolve in DNS (21 November 2026). For 173 domains the homepage was read to confirm ownership; the other 77 could not be read and were assigned by the domain matching the organisation's official name. 68 of 318 candidates were dropped as duplicates, out of scope or not matching their organisation
MeasurementsInfected devices and employee devices, breach-database, stealer-log and combolist records, dark-web chat and forum mentions, lookalike domains, exposed documents and current credential-market listings, using the same data Atlas uses; plus public DNS, TLS and HTTP header checks
DateCounts read 21 November 2026. Device, credential and listing counts are all records held on that date, regardless of capture date (cumulative, not 2026-only). Mention counts cover the 365 days to 18 November 2026; lookalike counts cover the last 30 days
Not deduplicatedAcross sources, across organisations or across people. One person can appear in several sources; one device can hold logins for several organisations
Not representativeResults describe this list. They are not national prevalence rates

3.2 National rating and current listings by sector

Atlas rates each organisation from 0 (no risk observed) to 100. Atlas gives the 250 organisations a national headline rating of 53 on this 0-100 scale; it is a summary rating, not an average. By sector, the report gives the signal counts.

How to read Atlas ratings.

TermMeaning
HeadlineThe national summary rating Atlas reports; it is not an average
Current listingA credential tied to the domain on sale at the time of the check
Listing historyA credential tied to the domain was offered for sale at some earlier time

205 organisations had candidate lookalike matches; those matches were not all validated.

Credentials and infected devices are common in every sector; current listings vary by sector

Share of organisations in each sector with the signal. Current credential listings are shown in coral.

InfecteddevicesEmployeedevicesCredentialrecordsCurrentlistingListinghistoryLookalikes(30 days)ExposeddocumentsMedia and entertainment (8)100%75%88%62%62%75%62%Technology (11)91%91%100%55%55%100%82%Government (68)94%75%96%54%53%85%59%Telecom (6)67%67%100%50%50%83%33%Banking and finance (35)100%83%100%46%37%94%66%Education (18)100%100%100%44%44%89%78%Hospitality and tourism (9)89%44%100%44%44%78%56%Retail and holdings (16)100%75%100%44%38%69%81%Transport and logistics (19)89%79%95%42%32%79%58%Healthcare (11)100%82%100%36%36%64%55%Insurance (11)100%82%100%27%27%73%36%Manufacturing and industry (9)89%78%78%22%11%56%56%Energy and utilities (19)84%84%89%21%16%79%53%Real estate and construction (10)80%70%100%20%10%80%70%

Source: Brandefense Blackhole associations and Atlas ratings for 250 organisations, read 21 November 2026 [S2][S3]. Records are cumulative, not 2026-only.

SectorOrgsOrgs with a current credential listing
Government6837
Banking and finance3516
Energy and utilities194
Transport and logistics198
Education188
Retail and holdings167
Insurance113
Technology116
Healthcare114
Real estate and construction102
Manufacturing and industry92
Hospitality and tourism94
Media and entertainment85
Telecom63
All 250250109

Reading the table. Triage from the listing column. Government (37 of 68) and banking and finance (16 of 35) have the most organisations with a current listing. In media (5 of 8), telecom (3 of 6) and technology (6 of 11) half or more are listed, but all three sectors are small.

3.3 Devices and credentials

Government, transport and technology carry the most infected-device associations; universities hold most employee-classified devices
  • Employee-classified
  • Other (not employee-classified)
Government134,996 (4,124)Transport and logistics83,791 (1,619)Technology83,172 (2,717)Education55,123 (16,760)Retail and holdings52,138 (1,197)Telecom35,855 (793)Banking and finance30,306 (674)Energy and utilities23,099 (1,241)Media and entertainment6,016 (51)Healthcare5,357 (777)Insurance4,624 (80)Real estate and construction4,229 (97)Hospitality and tourism3,204 (188)Manufacturing and industry218 (97)

Source: Brandefense Blackhole associations and Atlas ratings for 250 organisations, read 21 November 2026 [S2][S3]. Records are cumulative, not 2026-only.

SectorOrgs with infected devicesDevices (employee)Credential recordsCredential share, two largest orgs
Government64 of 68134,996 (4,124)157,22657%
Transport and logistics17 of 1983,791 (1,619)232,30063%
Technology10 of 1183,172 (2,717)92,41471%
Education18 of 1855,123 (16,760)958,69058%
Retail and holdings16 of 1652,138 (1,197)65,41460%
Telecom4 of 635,855 (793)38,28894%
Banking and finance35 of 3530,306 (674)90,63831%
Energy and utilities16 of 1923,099 (1,241)76,22756%
Media and entertainment8 of 86,016 (51)10,70769%
Healthcare11 of 115,357 (777)43,26263%
Insurance11 of 114,624 (80)9,16261%
Real estate and construction8 of 104,229 (97)21,97958%
Hospitality and tourism8 of 93,204 (188)48,66985%
Manufacturing and industry8 of 9218 (97)11,33864%
All234 of 250522,128 (30,415)1,856,31430%

Device totals are lower bounds. Credential records split into 466,560 breach-database records, 579,220 stealer-log lines and 810,534 combolist entries. The infected devices hold more than 3.7 million captured credentials in total, for all services, not only the organisation's own.

What this means.

  • Most device associations sit outside the employee classification. 491,713 of 522,128 devices are not employee-classified. Many are most plausibly residents' and customers' own computers, though ownership is not established. They are a fraud and account-hijacking signal and do not by themselves establish an intrusion. The 30,415 employee-classified devices are the intrusion-relevant subset; both groups require validation.
  • Universities hold the employee-device problem. Education has 16,760 employee-classified devices, more than half of the national total in our list, and 958,690 credential records. Staff and students share domains, so "employee" here may include students.
  • Concentration is high. In telecom, two organisations hold 94% of credential records. A sector total is therefore a poor guide to a typical organisation.
  • The median organisation is modest. The median organisation has 274 infected devices and 782 credential records; the heaviest carry tens of thousands.

3.4 Current credential listings

109 of 250 organisations had at least one credential tied to their domain listed on a monitored credential market at the time of the check. Of those 109, 99 also have a listing history.

For a defender, a current listing is the most direct market signal that a login tied to the domain is on offer. Whether that login still works is exactly what validation must establish. The listing does not say how many accounts, whose accounts, or whether the account is active, protected by multi-factor authentication (MFA) or already reset. The decision it supports is "validate the account now", not "declare a breach".

3.5 Lookalike domains, exposed documents and mentions

  • Lookalikes: 205 organisations had at least one newly observed candidate lookalike domain in the last 30 days. Those matches were not all validated; validate each domain before acting. Lookalikes are candidates, not confirmed phishing sites.
  • Exposed documents: 154 organisations have at least one exposed document that references their domain (3,104 in total), most of them in government.
  • Mentions: 89 organisations were mentioned in dark-chat (messaging-channel) sources in the last 365 days and 24 in dark-web sources. Mention counts measure visibility, not hostility; news sites and portals linked in Telegram channels collect many.

3.6 Email and web hygiene

Most sectors enforce DMARC; telecom has the largest share without enforcement and government the largest number
  • DMARC enforced (quarantine or reject)
  • Not enforced (none, missing or invalid)
Technology11 of 11Energy and utilities18 of 19Real estate and construction9 of 10Manufacturing and industry8 of 9Banking and finance31 of 35Media and entertainment7 of 8Education15 of 18Healthcare9 of 11Transport and logistics15 of 19Hospitality and tourism7 of 9Government51 of 68Retail and holdings12 of 16Insurance8 of 11Telecom3 of 6

Source: Brandefense public DNS, TLS and homepage checks of 250 domains, 21 November 2026 [S4].

Results from our public DNS, TLS and homepage checks [S4]:

ControlResult (of 250 unless stated)Reading
DMARC reject120Spoofed mail from the domain should be refused
DMARC quarantine84Spoofed mail should go to spam
DMARC p=none or missing46 (36 none, 10 missing)No enforcement; spoofing the domain is easier
SPF ending -all / ~all / ?all / redirect / none170 / 69 / 1 / 3 / 77 domains publish no SPF policy
DKIM record found184Absence is not proof of no DKIM
DS record observed (DNSSEC delegation)12No DS record observed for 238 domains; a DS record alone does not prove a valid chain of trust
TLS certificate invalid8 of 222 checkedExpired, mismatched or untrusted certificates
HSTS (HTTP Strict Transport Security) on homepage143 of 173 reachableMost reachable sites force HTTPS for returning visitors
Mail provider106 Microsoft 365, 10 Google, 8 with no mail (MX) recordThe rest run their own or regional mail

Hygiene is stronger than exposure. 204 of 250 organisations (82%) enforce DMARC, including 31 of 35 in banking and finance and 51 of 68 government bodies. Telecom (3 of 6 without enforcement) and government (17 without enforcement) have the largest gaps (§12.1 row 8). On the passive hygiene index (Appendix A.5; 0-100, higher is weaker), insurance (38) and telecom (36) have the weakest hygiene index by sector and technology (17) and real estate (19) the strongest. Good email hygiene does not offset credential exposure: the listings in §3.4 concern logins, not spoofing.

Key takeaways

  1. 01

    Infected-device and credential associations are near-universal in the list; they call for validation, not alarm.

  2. 02

    109 of 250 organisations had a current credential listing; triage those listings first.

  3. 03

    DMARC enforcement is strong at 82%; DNSSEC delegation is rare at 12 of 250.

Chapter 4

What we see on the dark web

This chapter answers

What do criminals post about the UAE once bot spam is removed, and which offers matter to defenders?

130,477posts tagged as concerning the UAE, 1 January-20 November 2026

In short

Most UAE-tagged underground traffic is multi-country advertising in English, Russian and Chinese Telegram channels. After cleaning, about one in three posts remains, and most of those are card-checker output, account trading and multi-country data leaks naming the UAE among many countries. The UAE-specific offers that matter are real-estate customer data, identity and residence-card verification, and access to government web systems. Triage each claim by provenance before comment.

4.1 Universe card

ItemDefinition
SourceBrandefense Blackhole: Telegram channels and groups, a set of cybercrime forums, paste sites and Discord, collected continuously [S1]
Country definitionA country tag ("this post is about, targets or mentions the UAE"), plus forum posts mentioning the UAE
WindowPost time 1 January-20 November 2026 (November partial)
Tagged set130,477 posts counted
CoverageRelevant-post ranges cover January-July and November (65,544 tagged posts); August and October are covered only in part, and September posts were not available
Forum posts1,271 distinct forum posts mentioning the UAE
Relevant postsGiven as a range for January-July and November (Appendix A.2)
Not establishedThat a tagged post targets the UAE, that a claim is true, or that two posts concern the same file

4.2 Platforms, languages and volume

One account-trading bot family makes October the largest month; volume otherwise runs at about 6,000-17,000 tagged posts a month
  • Raw tagged posts
  • Cleaned posts (low to high estimate)
05,00010,00015,00020,00025,00030,00035,000Mostly account-trading bot posts6,157Jan2,829-2,9335,912Feb2,835-2,9709,823Mar4,861-4,9838,371Apr2,389-2,51310,916May1,694-1,76710,345Jun2,732-2,8259,742Jul4,547-4,66415,085Aug17,413Sep32,435Oct4,278Nov1,776-1,801

August to October have no relevant-post range: coverage for those months is incomplete. Source: Brandefense Blackhole, posts tagged as concerning the UAE, post dates 1 January-20 November 2026, November partial [S1]. Cleaned counts are an upper bound.

MeasureValue
Telegram share of tagged posts99.64% (130,007)
Forum posts381 tagged, plus 1,271 distinct forum posts mentioning the UAE
Paste, Discord39, 50
Russian / English / Chinese / Arabic36.0% / 35.4% / 24.0% / 1.6% of tagged posts (a post can carry more than one language)
Largest monthOctober, 32,435 posts, of which 19,924 were account-trading posts
Russian and English dominate the UAE tag; Arabic is under 2% of posts
  • Russian
  • English
  • Chinese
  • Arabic
05,00010,00015,00020,00025,000JanFebMarAprMayJunJulAugSepOctNovRussianEnglishChineseArabic

Telegram carries 99.64% of tagged posts. Language labels can overlap. Source: Brandefense Blackhole, posts tagged as concerning the UAE, post dates 1 January-20 November 2026, November partial [S1]. Cleaned counts are an upper bound.

October is a bot month, not an attack month. 61% of October's tagged posts were account-trading posts, dominated by repeated price-list templates. Chinese-language advertising inflated April-August in the same way. Saudi Arabia shows an even larger January-February spike (729,186 posts in two months), and Qatar an October spike (42,835), so spikes of this kind say more about bot campaigns than about a country.

Arabic is rare in the UAE underground we observe. Only 2,070 tagged posts (1.6%) are in Arabic. Criminal trade about the UAE runs mostly in English and Russian, aimed at a resident population that is itself multilingual (§2.1).

4.3 Crime families after cleaning

In January-July and November, the relevant (cleaned) posts number 23,663-24,456 of 65,544 tagged posts (36.1-37.3%), given as a range. Of 30 random relevant posts, 27 were crime-related, but only 10 named the UAE specifically. Cleaned counts are therefore an upper bound for UAE-specific criminal activity.

Card-checker output and account trading dominate the cleaned posts; access sales are rare
  • Cleaned posts
Card material and checker output9,555Financial-account trading6,003Data leaks and databases4,615Phishing and fraud services1,939KYC and identity documents959Malware and exploits464Illegal goods363Combolists182Stealer logs123DDoS and hacktivism115Ransomware mentions109Access sales106

Cleaned posts, January-July and November. Source: Brandefense Blackhole, posts tagged as concerning the UAE, post dates 1 January-20 November 2026, November partial [S1]. Cleaned counts are an upper bound.

Family (cleaned posts, January-July and November)PostsWhat dominates
Card material and checker output9,555Bot output testing cards, many issued by UAE banks (§8.2)
Financial-account trading6,003Bank, wallet and exchange accounts; mule recruitment
Data leaks and databases4,615Multi-country lead lists; a minority of UAE-specific datasets
Phishing and fraud services1,939Payment-link abuse, fraud tooling, "shooter" recruitment
KYC and identity documents959Residence-card and passport verification services
Malware and exploits464Tool sales; few UAE-specific
Combolists and stealer logs305Credential lines for UAE banks, portals and airlines
DDoS and hacktivism115March claims against federal sites (Chapter 6)
Access sales106Government and corporate web-system access (§4.5)
Other families472Illegal goods (363) and ransomware mentions (109)

Family counts are not compared across June 2026. A post can belong to more than one family.

4.4 UAE-specific data offers: real estate leads

Real-estate data was the most frequently advertised UAE-specific dataset category in the reviewed posts. Across the year, at least nine sellers listed data on property owners, tenants and portal users. Claims ranged from a 74,000-line owner list for one community to 986,506 account records from a UAE real-estate service, with password-related fields. Asking prices were low, up to 1,200 USD, and one set was posted free. A buyer asked for a multi-million-line agency database in February, before the April-May wave of listings.

DateOffer (claimed)PriceCard
2026-02-18Buyer seeks a multi-million-line Dubai agency CRMn/aB20
2026-04-02A Dubai developer's customer, sales and identity-document data100 USDB02
2026-04-13400,000 owner and tenant records attributed to a major developer, raised to 700,000 six days laternot statedB04
2026-05-06986,506 account records from a UAE real-estate servicefreeB06
2026-09-1049GB property-platform database, with a claim that it was then wipednot statedB05

One seller insisted its set was not the "public data" of Dubai owners that, it said, "everyone" sells, which concedes that such lists already circulate. That weakens the uniqueness of each claim but not the risk. Owner, tenant and transaction details are exactly what payment-instruction and fake-handover fraud needs.

Evidence card B20
OriginalI am looking for a big Realty Estate Agency database from United Arab Emirates (Dubai if i'm not wrong) with couple millions lines also in thread title was just domain name and description was said that base from CRM. I lost link to thread

Note. Demand for property data came before the April-May wave of developer and portal listings.

Held
A buyer looked for a multi-million-line Dubai real-estate agency CRM database seen earlier on the forum.
Not established
It does not establish that such a database exists.
Evidence card B04
OriginalI am selling here [major Dubai property developer] - owners & rentals information, Datasets have more than 400k records of owners and rentals and even they car information and even their parking and address, phone numbers, emails. and included 4gb of Docs. [...] is not public Data of Dubai owners which everyone sell

Note. Six days later the same alias raised the claim to 700,000 records covering a second developer.

Held
A seller advertised 400,000 owner and tenant records, with car and parking details, attributed to a major Dubai developer.
Not established
It does not establish the source system; the seller's own wording admits that similar Dubai owner lists already circulate.
Evidence card B02
Original[Dubai real-estate developer] is Real estate company in dubai [...] Price: 100$ [...] I got customers Info / sales info / id,passport pics + bank transactions / CRM

Note. A second alias offered the same CRM column set on another forum on 19 Apr, claiming 350GB from a sales-manager account.

Held
The same actor family offered a Dubai property developer's customer, sales and identity-document data for $100.
Not established
It does not establish the volume of records or that passport images are genuine.
Evidence card B06
OriginalUAE REAL ESTATE DATA REPORT [...] Total Records: 986,506 Region: United Arab Emirates Sector: Real Estate [...] Fields Observed • Name • Login Identifiers • Password-Related Values • Phone / Cell Numbers • Email Addresses • WhatsApp Information • IP Addresses

Note. Part of a year-long cluster of at least nine property-owner and real-estate datasets.

Held
A post advertised a claimed dataset containing 986,506 records from a UAE real-estate service, with password-related and contact fields.
Not established
It does not establish which platform the records came from; a later repost named a UAE property portal without evidence.

4.5 Government-themed offers and recirculated material

Government-themed offers in 2026 were mostly entry points and recirculated files, not fresh national datasets.

  • Recirculation. A student dataset that posters date to March 2025 was reposted on at least five forums from January to May (B07).
  • Access. Super-administrator access to an emirate's finance department web system was offered for 800 USD in April (B08).
  • Reconnaissance. A March package mapped a government department's AI service back-ends and an end-of-life PHP portal (B09).
  • Population lists. One actor advertised 30,000 police personnel records in February and 180,000 records on foreign residents of one nationality two weeks later (B10).
  • Credential lines. Automated log uploads carried credential lines for a government e-services login page (B12).
  • Exposure lists. A free list of about 185,000 internet-exposed camera streams in the UAE was shared on 5 March (B11).
Evidence card B07
OriginalIn March 2025, [an education organisation] experienced a significant data breach. The compromised dataset includes [...] This breach primarily affects students

Note. Reposted on at least five forums between January and May; download links were reported dead in several threads.

Held
A student dataset attributed to an education organisation was reposted for free download in January 2026.
Not established
It does not establish a new 2026 incident; the post dates the original claim to March 2025.
Evidence card B08
OriginalToday I'm selling UAE [an emirate's finance department] Super Administrator Access. Proof: [link removed] Price: 800 USD Contact (session only): [contact removed]

Note. Lowest-priced government access offer in the corpus.

Held
A seller offered super-administrator access to an emirate's finance department web system for $800.
Not established
It does not establish which application the access covers or whether it was still valid.
Evidence card B09
OriginalI've spent the last week mapping [an emirate government department] [...] AI BRAIN: [exposed LLM-orchestration back-ends]. These are the backends for [a government AI service] [...] THE HOLE: [an end-of-life PHP portal] [...] ADMIN ACCESS: [portal instances with authentication misconfigurations].

Note. Early example of AI-platform reconnaissance being sold against a government AI service.

Held
A seller offered a reconnaissance package on a government department's AI and web stack, naming exposed LLM-orchestration endpoints and an end-of-life PHP portal.
Not established
It does not establish that the seller got in or took any data.
Evidence card B12
Original[a government e-services portal] Uploaded by X FORUMS [...] Content Type: URL / Email / Password Combo

Note. The same bot posted log extracts for a UAE retail bank, a UAE airline and luxury e-commerce sites.

Held
Credential lines for a government e-services login page appeared in an automated log upload.
Not established
It does not establish that the accounts were valid or that the portal itself was breached; such lines usually come from infected user devices.
Evidence card B10
Original30,000 Police Personnel Information(PII) (Full Details) from United Arab Emirates Screenshot as proof: [link removed] for more proof just contact us No Telegram - No TOX - Just Session

Note. Two weeks later the same alias listed 180,000 records on foreign residents of one nationality, in the same format and with session-only contact.

Held
An actor advertised personal data on 30,000 UAE police personnel, with screenshot proof only.
Not established
It does not establish the data's origin, completeness or accuracy.
Evidence card B11
OriginalI'm sharing this dataset, which contains a curated list of publicly accessible IoT devices within the United Arab Emirates (UAE) infrastructure that expose their video streams via RTSP (protected/unprotected) [...] UAE IoT | Vuls Server:Port | RTSP CAM | 185K

Note. Shared on 5 March; relevant to physical-security camera exposure.

Held
A free list of about 185,000 UAE internet-exposed camera stream endpoints, built from scanning, was shared during the heightened period the Council described.
Not established
It does not establish that any stream was accessed without authorisation.

4.6 Case studies

Each case sets out the claim, what we can establish and a proportionate response, with chronology, alternatives and limits where the evidence supports them. Case responses are starting points; the owned actions, with owners and completion evidence, are in §12.1.

A

Case A

An insurer's customer file posted on Telegram and three forums

Evidence card B0130 Jan 2026Breach forumInsurance
Claim unverified
Claim
A seller advertised about 80,000 customer and broker records attributed to a UAE insurer for 200 USD, filtered, it said, from 500,000 rows. Listed fields include national ID numbers, contact details and amounts paid.
Chronology
A Telegram teaser on 28 January; the full listing on 30 January; relisted on two further forums on 2 and 25 April by the same alias.
What we can establish
That one alias kept the same organisation-specific listing alive for three months. The seller wrote that access was lost early, which fits a short-lived login rather than lasting access.
Alternatives
Data from a broker, a third-party CRM vendor or an aggregator; recycled older records.
Limits
We did not obtain the sample. Neither the insurer nor an authority had commented by our cut-off.
Response
Insurers and brokers should review CRM and payment-portal access logs for January 2026, rotate integration credentials and prepare for phishing that quotes policy details (§12.1 rows 14-15).
Bottom line

Prepare for possible misuse of the advertised fields; check CRM and broker access before anyone speaks of a breach.

B

Case B

Two listings name an emirate's transport authority

Evidence card B0315 Nov 2026Breach forumGovernment, transport
Claim unverified
Claim
On 25 April one seller offered 301 files of permits, drawings and email for 800 USD. On 15 November a different seller listed a 50GB "database breach" for 5,000 USD, claiming 450,000 resident service records and 100,000 driver records with ID, passport and visa fields.
What we can establish
Two unrelated aliases named the same state body seven months apart and described different data: project documents, then an identity-linked customer dataset. No sample was published in the posts we read.
Alternatives
Contractor or consultant mailboxes for the April files; a field list built from other identity-linked sources, or invented to raise the price, for November.
Limits
No authority statement had addressed either listing by our cut-off.
Response
The authority and its contractors should review document-management and email exposure from the second quarter. Residents should be warned about impersonation using licence and visa details if a sample is verified (§12.1 rows 4 and 15).
Bottom line

Two unrelated sellers named the same body; verify any sample before comment and prepare resident warnings.

Evidence card B01
OriginalWelcome To Another UAE Data breach [UAE insurer] (80k record) [...] Price: 200$ [...] CRM (Payments invoice, customers info, brokers info) UAE Id card, full name, email, phone number, address, paid amount [...] the total was 500k record i filtered so i got 80k [...] i lost the access early

Note. Same listing posted on Telegram and three forums Jan-Apr; the alias links it to a Telegram handle that also advertised a Dubai developer dataset.

Held
A seller advertised an 80,000-record customer and broker CRM extract attributed to a UAE insurer for $200, listing national ID numbers among the fields.
Not established
It does not establish that the data came from the insurer's systems or that any sale took place.
Evidence card B03
Original[an emirate's transport authority] Database Breach __50GB [...] Price : $5K Exposed Services and Records : 1. Citizen and Resident Service (450K Unique Records) [...] 2. Drivers Service (100K unique Records + 35K Driver License PDF)

Note. An earlier, smaller listing (301 files, $800) for the same authority appeared on another forum on 25 Apr under a different alias.

Held
A seller listed a 50GB dataset attributed to an emirate's transport authority for $5,000, with a field list that includes ID, passport and visa numbers.
Not established
It does not establish that the authority's systems were accessed; the field list could be assembled from other sources.
C

Case C

Real-estate data as a market (B04, B06)

Real estate
Market observed
Claim
At least nine sellers listed owner, tenant, developer and portal data during the year (§4.4).
What we can establish
Real estate produced more UAE-specific organisation-level and population-level listings than any other sector in our data. Demand posts preceded the supply wave.
Alternatives
Many sets are probably rebuilt from broker lists, scraped portals and older extracts already in circulation.
Limits
Owner lists overlap heavily; record counts are claimed, not verified.
Response
Developers, brokers and portals should review CRM exports and partner access, and warn owners about payment-instruction and fake-handover fraud (§12.1 rows 14-15).
Bottom line

Owner and tenant data circulates widely; protect owners against payment-instruction and handover fraud.

D

Case D

A 2025 student dataset recirculates

Evidence card B0726 Jan 2026Breach forumEducation
Recirculated data
Claim
A student dataset with IDs, contact details, grades and school details, attributed to an education organisation, was reposted for free download.
What we can establish
Every poster frames it as the same March 2025 event; several threads report dead links. Nothing in our data points to a new 2026 intrusion.
Alternatives
A school-management vendor or a single platform as the original source.
Response
Schools should expect phishing aimed at students and parents that quotes school and grade details, and check whether any credential fields still work (§12.1 rows 2 and 15).
Bottom line

A 2025 claim keeps circulating; expect school-themed phishing and reset any reused credentials.

E

Case E

Access and reconnaissance offers against emirate government bodies (B08, B09)

Government
Offer unverified
Claim
Super-administrator access to a finance department web system (800 USD, April) and a reconnaissance package on a government department's AI and web stack (March).
What we can establish
Separate sellers offered entry points into government web and AI systems rather than finished datasets. The March package is the clearest example in our data of AI-platform reconnaissance offered for sale.
Alternatives
Access to a low-value sub-application; reconnaissance built from public scanning only.
Limits
No proof screenshots were available to us; validity and scope are unknown.
Response
Government entities should inventory internet-facing AI orchestration endpoints and end-of-life portals, enforce single sign-on on content-management platforms and remove local administrator accounts (§12.1 row 4).
Bottom line

Entry points, not datasets, were on sale; inventory internet-facing admin and AI endpoints.

F

Case F

A confirmed retail-loyalty incident and a leak-site listing in the same week

Retail
Incident confirmed by the company
Claim
On 10 November a ransomware leak-site group listed Landmark Group, the Dubai-based retail group, according to Ransompedia [S5].
Official account
On 11 November Landmark Group said it had identified unauthorised access to one of its systems affecting members of its Shukran loyalty programme. It said names, contact details and dates of birth may have been exposed, card details were not affected, and statutory and law-enforcement authorities had been informed [S24][S25].
What we can establish
A confirmed incident at the company and a leak-site claim against it within a day. The company did not mention a ransomware group, so we have not established that the two refer to the same event.
Response
Loyalty-programme members should expect phishing that quotes their name and birth date. Retailers running loyalty platforms should treat them as identity systems: monitor exports, protect administrator access with MFA and prepare member notices in advance (§12.1 rows 14-15).
Bottom line

A confirmed loyalty-platform incident; members' names and birth dates may have been exposed, so expect phishing that quotes them.

4.7 What the forums add

Forums contributed only 381 tagged posts, but they carry almost all organisation-specific claims (Cases A-E). Most forum hits are still global lead lists that name the UAE among dozens of countries. Buyers also posted requests: for agency CRM data (B20), an international airport operator's customer data and an "Emirates ID database" in November. Demand for UAE identity and property data is itself a finding.

Key takeaways

  1. 01

    Raw volume is dominated by multi-country bot templates; read cleaned counts as an upper bound.

  2. 02

    Real-estate data is the most frequently advertised UAE-specific category in the reviewed posts; prepare owners for payment-instruction fraud.

  3. 03

    Government-themed offers are mostly access, reconnaissance and recirculated files; triage provenance before comment.

Chapter 5

Targeting examples by sector

This chapter answers

Which UAE sectors are named in criminal and hacktivist posts, and what kind of response does each one need?

10sectors with observed activity, from government to real estate

In short

The posts below show how criminal and hacktivist actors talk about UAE organisations. Hacktivist claimants named high-profile state, energy and transport targets and claimed disruption. Criminal sellers named real-estate, insurance, education and transport data, and treated the UAE as a market for accounts and identities. Official reports are cited separately. Verify each claim with the named organisation before escalating, and start with the sector's first response.

Victims are described by role under the policy in Appendix A.9, except where an incident was officially confirmed and widely reported. Examples come from the cleaned corpus, the forum posts mentioning the UAE and public reporting. The first responses are starting points; the owned actions, with owners and completion evidence, are in §12.1 (rows 2-4, 6, 14-19).

Government

DDoS claimdestructive claimaccess salereconnaissancecredential lines

Example of observed activity (anonymised)

DDoS claims against federal government websites (Mar-Apr, Chapter 6); a hack-and-leak and wiper claim against several public-sector bodies in one emirate (Apr, unconfirmed); super-administrator access to a finance department system for 800 USD (Apr); AI-stack reconnaissance (Mar); credential lines for a government e-services login page (Aug); two listings against a transport authority (Apr, Nov)

What it means

Availability, citizen-data integrity and administrator access are the three exposures

First responsePre-agree status statements; enforce single sign-on and MFA on administrator interfaces

Real estate

Data saleleakdestructive claim

Example of observed activity (anonymised)

At least nine owner, tenant, developer and portal datasets (Jan-Nov); a buyer seeking an agency CRM (Feb); a wipe claim against a property platform (Sep)

What it means

The most frequently advertised UAE-specific data in the reviewed posts; feeds payment-instruction and handover fraud

First responseReview CRM exports and partner access; warn owners about payment-change requests

Banking and payments

Cardingmule accountscash-outcredentials

Example of observed activity (anonymised)

Card-checker output naming 14 UAE issuers (Feb-Mar peak); a finance conference's attendee identity documents left exposed in a vendor's storage, confirmed and secured by the organiser (Feb) [S65]; mule recruitment for business and personal accounts at named banks; payment-link and terminal cash-out; credential lines for a retail bank's login

What it means

Fraud tooling dominates; intrusion-relevant exposure sits in device data (Chapter 9)

First responseTriage current credential listings, then employee devices; monitor merchants for cash-out patterns

Energy and utilities

Leak claimDDoS claimOT (operational technology) claim

Example of observed activity (anonymised)

A relayed 1.3 TB leak claim against an emirate's oil company (Mar); DDoS lists naming an oil and gas company and a utility (Mar); an unspecified "electricity systems" intrusion claim (Jun)

What it means

The Council's wiper advisory names energy among targeted sectors [S11]

First responseVerify OT claims with the system owner; test offline backups and wiper response

Transport and aviation

Intrusion claimleak-site listingaccount resale

Example of observed activity (anonymised)

A relayed claim of access to an international airport operator (Mar, repeated Aug); a port claim (May); extortion listings against an airline caterer and a low-cost airline (Aug, Oct); loyalty-miles accounts resold

What it means

Passenger and identity documents are the material exposure

First responseWatch loyalty and customer accounts; review partner and booking-system credentials

Insurance

Data sale

Example of observed activity (anonymised)

An 80,000-record customer and broker file posted on Telegram and three forums (Jan-Apr; Case A)

What it means

Policy and payment details make customer phishing credible

First responseReview CRM access logs; prepare customer notices

Education

Recirculated datadata claimsransomware listings

Example of observed activity (anonymised)

A 2025 student dataset reposted (Jan-May); a school-management dump and passport sets claimed against school groups; eight leak-site listings in education

What it means

Student and parent data supports phishing and identity fraud

First responseCheck credential fields in old datasets; reset where reused

Healthcare

Data sale claimextortion listing

Example of observed activity (anonymised)

A relayed sale of files attributed to an emirate's health authority (Apr); leak-site listings naming three hospital groups by one group whose listings we could not corroborate (Feb)

What it means

Health identifiers do not expire; verify before notification

First responseCompare claimed schemas with real systems before any notice

Retail and consumer

Confirmed incidentlistingaccess sale

Example of observed activity (anonymised)

A confirmed loyalty-programme incident at Landmark Group and a leak-site listing the same week (Nov; Case F); a grocery platform's access offered for 100 USD (Jun)

What it means

Loyalty platforms are identity systems

First responseProtect loyalty-admin access with MFA; monitor bulk exports

Telecom

SIM servicesphishingdata claim

Example of observed activity (anonymised)

SIM and virtual +971 number sales; a phishing kit aimed at a national operator; an unsupported claim of a 7-million-record operator database

What it means

SIM and number services connect to account-recovery fraud

First responseTighten SIM-swap and number-port checks (§12.1 row 18)

Reading across sectors. Organisation-specific claims fall into two groups. Hacktivist claimants named high-profile targets (state portals, energy, ports and airports) and claimed disruption or destruction, with most activity in March and April. Financially motivated sellers named real-estate, insurance and transport data, and otherwise treated the UAE as a market for verified accounts and identities. The second group was active all year and is less visible in the press.

Key takeaways

  1. 01

    Hacktivist claimants named high-profile state, energy and transport targets, mostly in March-April.

  2. 02

    Real estate was the most frequently advertised UAE-specific data category in the reviewed posts.

  3. 03

    For banks and telecoms, the posts point to account-opening, mule and SIM controls rather than to intrusion.

Chapter 6

Hacktivism, DDoS and destructive claims

This chapter answers

Who claimed attacks on UAE targets in 2026, what did the authorities say, and how should an organisation prepare for the next claim?

10DDoS claims in the actor posts we read against UAE targets, all between 2 March and 8 April

In short

Hacktivist claims against the UAE clustered in March and April, during the heightened period the national cybersecurity authority described. Most were short DDoS claims against federal and emirate websites, backed only by availability-check links. Larger hack-and-leak and wiper claims against state bodies, an oil company, a port and an airport reached us only through relays and were not confirmed by the named bodies. Pre-agree who confirms service status and test offline backups.

6.1 Timeline

  1. 18 Feb 2026
    UAE Cybersecurity Council

    128 confirmed incidents since 1 January; defacement 38.3% and data leaks 25.8% of the total

  2. 22 Feb 2026
    RipperSec

    Claims leaks of four UAE company databases

  3. 28 Feb 2026
    UAE Cybersecurity Council

    Start of the heightened period later described by the Council's head (to early April)

  4. 2 Mar 2026
    313 Team

    Claims a one-hour DDoS on two federal government websites; further claims to 11 March against several federal bodies

  5. 3 Mar 2026
    Leak-monitor bots

    Relay a Handala claim of 1.3 TB from an oil company in one emirate

  6. 6 Mar 2026
    DieNet (own bot message, reposted)

    DDoS claims against federal government websites

  7. 9 Mar 2026
    Keymous+

    First UAE DDoS target list; six federal sites with availability-check links on 12 March; further lists to 8 April, including energy and utility sites

  8. 19 Mar 2026
    UAE Cybersecurity Council

    Public warning on destructive wiper malware (press report updated 19 March)

  9. 27 Mar 2026
    coderx

    Posts a 16.6 GB database it attributes to a Dubai facilities-management company

  10. 30 Mar 2026
    Monitor channels

    Relay a Nasir Security claim of access to an international airport operator, with passport images claimed

  11. 4 Apr 2026
    UAE Cybersecurity Council

    Advisory on a destructive wiper campaign across sectors; "some organizations have already been impacted"

  12. 12 Apr 2026
    Security press

    Handala claims wiper and data theft at several public-sector bodies in one emirate: 6 PB destroyed, 149 TB stolen

  13. 4 May 2026
    Aligned channels

    Relay a Handala claim against an emirate's port

  14. 1 Jun 2026
    Golden Falcon

    Claims it has begun an intrusion into UAE electricity systems

  15. 10 Sep 2026
    Aggregator account

    Claims export and deletion of a UAE property platform's 49 GB database

  16. 15 Sep 2026
    Head of the UAE Cybersecurity Council

    A hacker who exploited an unpatched vulnerability demanded 5 million USD from a private-sector organisation

  17. 18 Nov 2026
    Head of the UAE Cybersecurity Council

    More than 40 groups from over 20 countries tried to exploit the regional crisis

Dark markers are actor posts, outlined markers are relays by third parties, coral markers are official statements. Dates are post or statement dates. Sources: actor posts and relays [S1]; official statements [S9][S12][S11][S17][S22]; Handala's April claim [S26].

6.2 March-April: many short DDoS claims

The DDoS claims were short, public and thinly evidenced. We hold 22 actor posts claiming action against UAE targets. In the posts we read, all ten DDoS claims among them fall between 2 March and 8 April, from 313 Team, Keymous+ and Cyber Fattah. DieNet's claims reached us only as reposts of its bot messages (from 1 March) and are not among the ten. The targets were federal government websites, emirate government and media-office sites, energy and utility websites and one bank's public site. The proof offered was availability-check links: snapshots of reachability from a handful of probe locations. They can record a moment of unreachability, not an outage.

Evidence card B21
Originalهجوم سيبراني استهدف خوادم الرئيسية لحكومة الامارات حيث ادى الهجوم الى تعطل [موقع حكومي اتحادي 1] و[موقع حكومي اتحادي 2] [...] سيستمر الهجوم لمدة ساعة كاملة.
TranslationA cyberattack targeted the main servers of the UAE government, disrupting [federal government website 1] and [federal government website 2] [...] The attack will last a full hour.

Note. One of four 313 Team claims (2-11 Mar) against federal and emirate government websites.

Held
The group claimed a one-hour DDoS against two federal government websites on 2 March.
Not established
It does not establish any outage beyond the actor's own Check-Host links.
Evidence card B22
OriginalUnited Arab Emirates : [federal government website] Check Host [...] [federal ministry 1] Check Host [...] [federal ministry 2] Check Host [...] [federal ministry 3] Check Host [...] [federal ministry 4] Check Host [...] [federal ministry 5] Check Host

Note. Keymous+ posted at least five UAE target lists between 9 Mar and 8 Apr, including an oil and gas company and a utility.

Held
Keymous+ listed six federal government sites as DDoS targets, with Check-Host links offered as proof.
Not established
It does not establish service impact; Check-Host results capture a moment from a few probe locations.

Independent measurement confirms more DDoS, mostly low-volume. StormWall reported that the UAE's share of regional DDoS activity rose from 14% to 26% between the first quarters of 2025 and 2026. It put attacks on the UAE up 86% year on year [S30]. Help AG counted 236,560 DDoS attacks on UAE networks in the first half of 2026, 91% of them low-volume [S35]. Neither source reported a lasting national outage.

6.3 Destructive and hack-and-leak claims: claim against official account

The most serious claims came from Handala, a brand that Security Affairs describes as presenting itself as a pro-Palestinian hacktivist group but widely seen as a front for an Iran-backed actor [S26]. Its posts reached our data only through relays.

PointHandala's claim (12-13 April)Official accountIndependent reporting
TargetsSeveral public-sector bodies in one emirateNo statement addressing the claim found by our cut-offClaims "remain unverified" [S26]
Effect6 PB of data destroyedThe Council's 4 April advisory described an active regional wiper campaign without naming victims [S11]Not measured
Data149 TB stolenNot statedNot verified [S26]
AttributionOwn claimThe Council's head made attribution statements on other occasions (§2.4)Front for an Iran-backed actor, as described by Security Affairs [S26]

What we can establish. A brand that Security Affairs links to an Iran-backed actor [S26] claimed a wiper attack on state bodies, and the national authority had warned of an active wiper campaign eight days earlier. The claimed volumes are very large for bodies of this kind, and no named body confirmed an incident by our cut-off. We do not compute or imply a ratio between claim and reality.

The same pattern held for the other large claims. Handala claimed 1.3 TB from an oil company in one emirate (3 March) and data from a port (4 May). Nasir Security claimed months of access to an international airport operator (30 March, repeated in August), and it also claimed a customs authority (August) [S66]. All were relayed but not confirmed by the named bodies by our cut-off. Public monitors reported both the port and airport claims as allegations [S27][S28].

The private-sector case the authorities did describe. On 15 September the head of the Council said a hacker exploited an unpatched vulnerability at an unnamed private-sector organisation, claimed access to its systems, threatened to expose its data and demanded 5 million USD. Khaleej Times reported that some information was later published on the dark web; Gulf News reported that the leak was prevented [S17][S67]. The organisation was not named.

Evidence card B23
Original16GB [Dubai facilities-management company] DATABASE [...] Leaking 16GB Database Of [Dubai facilities-management company] [...] Number Of Files: 1 Original Size: 16.6 GB Compressed Size: 696 MB

Note. The post's political statements are left out here.

Held
An actor posted a 16.6GB database it attributed to a Dubai facilities-management company.
Not established
It does not establish that the file is what the actor says it is.
Evidence card B24
OriginalThe attack on the UAE's electricity systems has begun [...] It was just a small warning, and this time we just agreed to read the data

Note. Relayed by a monitor channel the next day; no follow-up in the corpus.

Held
A group claimed it had begun an intrusion into UAE electricity systems and limited itself to reading data.
Not established
It does not name an operator or system, show proof, or establish any effect on power supply.

The only wiper-style claim against a UAE company in our data came later, in September, from an actor who said it exported and then deleted a property platform's database (B05). No outage or confirmation followed in the sources we reviewed.

Evidence card B05
Original49GB of [UAE real-estate platform] Database Leaks [...] today I [contact removed] gained access to a database of a real estate company in the United Arab Emirates. After exporting the entire database i also wiping everything out.

Note. This is the only wiper-style claim against a UAE company in the corpus.

Held
An actor claimed to have exported a UAE property platform's 49GB database and then deleted it.
Not established
It does not establish that any deletion took place or that the platform lost service.

6.4 Lessons for defenders

  1. Prepare for wipers, not only for encryption. The Council's own advisory describes destructive malware entering through phishing, stolen VPN credentials and unpatched systems [S11]. Test that offline backups restore within the recovery time you have promised (§12.1 rows 4, 6 and 17).
  2. Pre-agree the public line. Hacktivist numbers are designed to be quoted. Decide in advance who confirms service status, within what time and through which channel (§12.1 row 16).
  3. Protect portals upstream. Short, repeated DDoS claims target public portals. Contract upstream mitigation before the next heightened period (§12.1 row 9).
  4. Verify OT claims before escalation. A claim of access to "electricity systems" without a named system owner is a reason to check, not to announce (B24; §12.1 row 16).

Key takeaways

  1. 01

    Hacktivist DDoS claims clustered in March-April and rested on availability-check links.

  2. 02

    Destructive and hack-and-leak claims against state bodies, energy, a port and an airport stayed unconfirmed by the named bodies.

  3. 03

    The authority's own wiper advisory names the controls: phishing defence, VPN credential hygiene, patching and restorable backups.

Chapter 7

Threat actors

This chapter answers

Which actor types matter for the UAE, how are they connected, and what does public reporting say about each?

4actor types: state-linked espionage, destructive hack-and-leak, ransomware and fraud networks

In short

Four actor types matter for the UAE in 2026. Vendors reported state-linked espionage against UAE entities through phishing and job lures. A hack-and-leak brand claimed destructive attacks on state bodies, unconfirmed by them. Ransomware and extortion groups listed dozens of UAE companies, mostly private firms. Fraud networks abused UAE payment and identity channels. Patch edge systems; hunt side-loaded DLLs, remote-management tools and unusual outbound traffic from mail and CRM servers; verify every claim before comment.

Each profile separates what the source observed, the attribution as the source states it, what remains unresolved and what it means for organisations. Confidence applies to a specific proposition, not to an actor as a whole. Attributions are the sources' own; we make none.

7.1 How the actors connect

The map links actors only where we hold evidence, and each line says what kind: the actor's own post, a third-party relay, an official statement or public reporting. A line is an association, not proof of a common operator.

  • Own post
  • Relay
  • Official statement
  • Public reporting
  • Our observation
MuddyWaterUnit 42 (vendor research)Screening Serpens
HandalaRelay and monitor channelsNasir Security
DieNetRelay and monitor channels
313 Team
own post credited jointly (11 Mar)
DDoS-for-hire brand

No evidenced link to other actors

Keymous+

7.2 State-linked espionage

MuddyWater (Boggy Serpens)

Boggy Serpens (Unit 42 name)
Espionage (state-linked per vendor)Attributed by Unit 42 to Iran's Ministry of Intelligence and Security

UAE-relevant reporting, 2026

  1. Jan-Feb

    Wave against a Middle East marine and energy company; one lure used dirham payroll records

  2. Mar

    Unit 42 lists the UAE among countries struck by recent campaigns

Targeted sectors

Government and corporate entities; a marine and energy company in the region

Seen in public reporting

  • [S31] Unit 42 (16 Mar 2026): attribution as stated; phishing from hijacked official and corporate mail accounts; remote-management tools (Atera, ScreenConnect, SimpleHelp) in earlier campaigns; custom implants in 2025-26

Our assessment

The UAE-relevant risk is phishing sent from trusted, hijacked mailboxes. In earlier campaigns legitimate remote-management tools followed, blending with IT traffic; in 2025-26 the vendor reports custom implants.

ConfidenceVendor attribution; UAE targeting stated by the vendor

Screening Serpens

UNC1549, Smoke Sandstorm, Iranian Dream Job (per Unit 42)
Espionage (state-linked per vendor)Iran-nexus, per Unit 42 (moderate-high confidence that the campaigns are this group's)

UAE-relevant reporting, 2026

  1. Apr

    A new variant that may have targeted an entity in the UAE

  2. May

    Unit 42 reports targeting of entities in the US, Israel and the UAE

Targeted sectors

Entities in the UAE (sector not published)

Seen in public reporting

  • [S32] Unit 42 (22 May 2026): recruitment and fake meeting-invite lures; MiniUpdate and MiniJunk V2 malware; DLL side-loading and AppDomainManager hijacking

Our assessment

Job-offer and meeting-invite lures aimed at individual staff; detection rests on endpoint telemetry for side-loaded DLLs in user-writable paths.

ConfidenceModerate-high (vendor)

Techniques named in the vendor research, by tactic

Initial access
(no ID given)Phishing sent from hijacked official and corporate mailboxes (Unit 42, MuddyWater)
Command and control
T1219Remote access software: Atera, ScreenConnect, SimpleHelp, in earlier campaigns (Unit 42, MuddyWater)
Defence evasion
T1055.012Process hollowing (Unit 42, MuddyWater)
Persistence / defence evasion
T1574.001DLL side-loading, as labelled by Unit 42 (Screening Serpens)
T1574.014AppDomainManager hijacking (Unit 42, Screening Serpens)

Technique IDs as linked in Unit 42's reports of 16 March and 22 May 2026. The phishing row has no ID in the source. [S12]

An unattributed intrusion into a defence company. ESET reported the compromise of a defence company in the UAE through a SmartOffice CRM server, followed by custom post-exploitation and reverse-proxy tools. ESET listed it among lesser-known and unattributed clusters [S33]. No CVE was published for the entry point.

Internet-exposed cameras were targeted. Check Point reported a sharp rise in exploitation attempts against IP cameras in the UAE and other Gulf states from 28 February, from infrastructure it attributes to Iranian actors [S58]. The flaws it highlighted include CVE-2017-7921 in Hikvision cameras and CVE-2021-33044 in Dahua devices. NVD rates both 9.8, and both are in CISA's known-exploited catalogue [S59][S60]. Affected and fixed firmware differ by model (table below) [S68][S69]. A free list of about 185,000 exposed UAE camera streams circulated on 5 March (B11), and in November the head of the Council described attempts to hack home, farm and car cameras [S23]. Patch or remove internet exposure of camera management interfaces (§12.1 row 5).

CVEProduct seriesAffected firmwareFixed firmware
CVE-2017-7921Hikvision DS-2CD2xx2F-IV5.2.0 build 140721 to V5.4.0 build 160530V5.4.5 build 170123 or later
CVE-2017-7921Hikvision DS-2CD2xx0F-IV5.2.0 build 140721 to V5.4.0 build 160401V5.4.5 build 170123 or later
CVE-2017-7921Hikvision DS-2CD2xx2FWDV5.3.1 build 150410 to V5.4.4 build 161125V5.4.5 build 170124 or later
CVE-2017-7921Hikvision DS-2CD4x2xFWDV5.2.0 build 140721 to V5.4.0 build 160414V5.4.5 build 170228 or later
CVE-2017-7921Hikvision DS-2CD4xx5V5.2.0 build 140721 to V5.4.0 build 160421V5.4.5 build 170302 or later
CVE-2017-7921Hikvision DS-2DFxV5.2.0 build 140805 to V5.4.5 build 160928V5.4.9 build 170123 or later
CVE-2017-7921Hikvision DS-2CD63xxV5.0.9 build 140305 to V5.3.5 build 160106V5.4.5 build 170206 or later
CVE-2021-33044Dahua IPC-HX1XXX to HX8XXX and HUM7XXX camerasBuilds dated before June 2021Per-model firmware dated July 2021 or later, for example V2.820.0000000.33.R.210705 (HX1XXX)
CVE-2021-33044Dahua SD-series PTZ domes (SD1A1, SD22, SD49, SD50, SD52C, SD6AL)Builds dated before June 2021V2.812.0000007.0.R.210706 or later
CVE-2021-33044Dahua TPC thermal camerasBuilds dated before June 2021Per-model firmware dated July 2021, for example V2.630.0000000.6.R.210707 (TPC-BF1241)
CVE-2021-33044Dahua VTO and VTH intercomsBuilds dated before June 2021V4.300.0000003.0.R.210714 (VTO75X95X), V4.300.0000004.0.R.210715 (VTO65XXX), V4.500.0000002.0.R.210715 (VTH542XH)

Hikvision versions are those listed in the ICS-CERT advisory; devices running unauthorised firmware may not accept the update. Check the exact model against the advisory; one firmware version does not fix every model [S68][S69].

Unresolved. Victim identities, data taken and dwell time are not public for any of these cases. Meaning. The common entry routes are hijacked trusted mail accounts, recruitment lures and internet-facing business applications. Alert on new remote-management tools, on DLL side-loading from user-writable folders and on unusual outbound connections from CRM and mail servers (§12.1 rows 4 and 7).

7.3 Destructive hack-and-leak and hacktivist actors

Handala

Handala Hack
Hack-and-leak, destructive claimsPresents itself as pro-Palestinian; described by Security Affairs as widely seen as a front for an Iran-backed actor

2026 in the UAE

  1. 3 Mar

    Claim of 1.3 TB from an oil company in one emirate (relayed)

  2. 12-13 Apr

    Claim of wiper and theft at several public-sector bodies in one emirate: 6 PB destroyed, 149 TB stolen

  3. 4 May

    Claim against an emirate's port (relayed)

Claimed targets

State bodies, energy and a port

Seen in public reporting

  • [S26] Security Affairs (13 Apr 2026): the April claims remain unverified; describes the brand and its reported links
  • [S27] A security vendor's news page (May 2026) reported the port claim, citing only the group's own claims

Our assessment

The most consequential claimant by stated intent. None of its 2026 UAE claims was confirmed by the named bodies by our cut-off; its posts reached our data only through relays.

ConfidenceHigh that the claims were made; impact unverified

Nasir Security

Nasir Resistance
Hack-and-leak claimsNot established; the group's own framing is political

2026 in the UAE

  1. 30-31 Mar

    Claim of months-long access to an international airport operator, with passport images and internal documents claimed (relayed)

  2. 22 Aug

    Renewed claim against the same operator

  3. 22 Aug

    Claim against a customs authority, posted the same day (S66)

Claimed targets

Aviation (airport operator); a customs authority

Seen in public reporting

  • [S28] A public breach monitor reported the March claim as alleged

Our assessment

A claimant focused on a few state-linked targets, whose evidence did not reach our data directly. The claim is a reason to check partner and document-management access, not to announce a breach.

ConfidenceClaim relayed; unverified

313 Team

Hacktivist (DDoS)Self-described religious and political framing (as reported by The National); self-declared targeting of six countries including the UAE; state links not verified (CloudSEK, via The National)

2026 in the UAE

  1. 2 Mar

    One-hour DDoS claim on two federal government websites (B21)

  2. 3 Mar

    DDoS claim on an emirate's media-office site

  3. 11 Mar

    DDoS claim on a federal government website, credited jointly with a DDoS-for-hire brand

Claimed targets

Federal and emirate government websites

In their words

“The attack will last a full hour.” B21

Seen in public reporting

  • [S29] The National (2 Mar 2026): the group publicly declared it was targeting the UAE among six countries; CloudSEK could not verify state links

Our assessment

A repeat DDoS claimant whose evidence is availability-check links. No claimed outage was confirmed by the named organisation or an authority.

ConfidenceHigh that it claimed; impact unverified

Keymous+

Hacktivist (DDoS)Not established

2026 in the UAE

  1. 9 Mar

    DDoS list: a federal ministry, an oil and gas company and a utility

  2. 12 Mar

    Six federal sites listed with availability-check links (B22)

  3. 25 Mar

    An oil and gas company and a utility in a ten-country energy list

  4. 6-8 Apr

    Four further federal ministry sites

Claimed targets

Federal ministries, energy and utility websites

In their words

“[federal government website] Check Host” B22

Seen in public reporting

  • No reputable public reporting on its UAE claims found in our sweep

Our assessment

The most frequent UAE DDoS claimant in our data (five lists). Its proof consists of probe snapshots only.

ConfidenceHigh that it claimed; impact unverified

DieNet

Hacktivist (DDoS)Not established; named in press coverage among groups claiming attacks in the region

2026 in the UAE

  1. 1-9 Mar

    Automated claim messages reposted by aligned channels: several federal government websites

Claimed targets

Federal government websites

Seen in public reporting

  • [S29] The National (2 Mar 2026): named among groups claiming attacks in the region; claims not independently verified

Our assessment

Claims reached us through reposts of the group's own bot messages; none was confirmed.

ConfidenceClaim relayed; unverified

Other claimants posted less often: RipperSec claimed four UAE company databases in February, Cyber Fattah a bank website in March, coderx a facilities-management database in March and Golden Falcon an electricity intrusion in June. None of these claims was confirmed by the named organisation or an authority, and we found no reputable public reporting that corroborates them.

7.4 Ransomware and extortion

UAE ransomware listings in 2026 far exceed those of four Gulf comparators
United Arab Emirates84Accepted listings, 1 Jan-20 Nov 2026
2025
48
All time
220

Groups in 2026Krybit, The Gentlemen, INC Ransom, N0n, 0apt

Saudi Arabia30Accepted listings, 1 Jan-20 Nov 2026
2025
27
All time
94

Groups in 2026The Gentlemen, N0n, Hyflock, APT73, INC Ransom

Qatar9Accepted listings, 1 Jan-20 Nov 2026
2025
5
All time
24

Groups in 2026Qilin, The Gentlemen, N0n, Akira, Payload

Kuwait7Accepted listings, 1 Jan-20 Nov 2026
2025
6
All time
29

Groups in 2026LockBit 5, N0n, The Gentlemen, Everest, Tengu

Oman9Accepted listings, 1 Jan-20 Nov 2026
2025
6
All time
27

Groups in 2026The Gentlemen, LockBit 5, Vexy-ransomware, Cl0p, Spirals

Source: Brandefense Ransompedia accepted listings, all dates, to 20 November 2026 [S5]; ransomware.live as a cross-check [S7].

Ransomware and extortion listings are frequent and mostly name private firms. Ransompedia holds 84 accepted UAE listings dated 1 January-20 November 2026, against 48 in all of 2025 [S5]. Five of the 84 are not victim organisations or are clearly not UAE-based (for example a group's own channel announcement), and five repeat an organisation already listed, leaving 74 distinct organisations. The four Gulf comparators had far fewer in the same window: Saudi Arabia 30, Qatar 9, Oman 9 and Kuwait 7. These comparator figures are raw listing counts, not cleaned the same way.

Measure (UAE, 2026 to 20 November)Value
Accepted listings84 (74 distinct plausible UAE organisations)
Most active groupsKrybit 8, The Gentlemen 7, INC Ransom 7, N0n 5, 0apt 4
Most named sectorsEducation 8, retail 8, construction 7, consulting 7
Busiest monthsOctober 13 and November (to the 20th) 12

A listing is a criminal claim. One group listed three hospital groups and a conglomerate on a single day in February; we could not corroborate its listings, and none of those organisations confirmed an incident. The only 2026 listing we can set against an official statement is the retail-loyalty case (Case F, §4.6). The Council's figures put ransomware at 7.8% of 128 confirmed incidents by mid-February [S9]. Leak-site listings and confirmed incidents measure different things, so the two figures cannot be reconciled.

A public tracker listed 70 UAE-labelled victims for the year [S7]. Several of its labels, and some of Ransompedia's, belong to companies based elsewhere. We removed entries that are clearly not UAE victim organisations; the remaining labels were not each verified.

7.5 Fraud networks and criminal personas

Criminal personas in our data are mostly sellers who name the UAE as one market among many. A smaller set posted UAE-specific offers. They include the seller of the insurer file (Case A), sellers of real-estate datasets (Case C) and two aliases behind the transport-authority listings (Case B). Others sold access and reconnaissance against government systems (Case E), and one actor offered population lists (B10). We print aliases as posted and withhold contacts. No shared concrete element links these personas to each other or to the hacktivist brands; any grouping of them would be an analytical model, not an observation.

Fraud groups outside our post data matter too. Recorded Future's reporting on the Tajin group describes abuse of UAE payment gateways for card fraud and money laundering [S34]. Police operations in April and October dismantled fraud centres and blocked thousands of bank accounts (§8.5).

Key takeaways

  1. 01

    Vendors reported state-linked espionage against UAE entities through hijacked mail accounts and job lures.

  2. 02

    Destructive hack-and-leak claims against state bodies stayed unconfirmed by them; prepare to verify before comment.

  3. 03

    Ransomware listings name mostly private firms, most often in education, retail, construction and consulting.

Chapter 8

The fraud economy

This chapter answers

How are UAE identities, accounts and payment channels turned into money, and what did the police report?

960+arrests in one 30-country fraud operation led by the Ministry of Interior (July-September)

In short

The most persistent UAE-specific fraud thread in our data is a market in residents' verified accounts: bank, wallet, remittance and exchange accounts tied to an Emirates ID or residence card. Around it sit card cash-out through payment links and terminals, KYC services and impersonation scams that the police warned about all year. Treat account-opening and recovery as fraud controls, and monitor payment-link merchants as closely as cardholders.

8.1 Bank, wallet and payment-account trading

UAE accounts tied to a real identity are the commodity. Channels recruiting "loaders" (people who fund or operate accounts for fraud) asked for fresh UAE remittance and wallet accounts linked to a valid Emirates ID, quoting confirmed limits of 10,000 AED (B13). A June post sought business accounts at two UAE banks, handed over "face to face" with SIM, debit card, Emirates ID and online-banking access, for 50,000-150,000 USD of transfers (B14). Russian-language forum posts recruited handlers for personal accounts at the same two banks (B15).

Evidence card B13
OriginalBring UAE [remittance app] Fresh only with emirates id 10k AED CONFIRM [...] guarantee

Note. Part of a January-November family of posts that recruit UAE residents to lend verified payment and wallet accounts.

Held
Loader channels sought fresh UAE remittance-app accounts tied to a valid Emirates ID with a 10,000 AED confirmed limit.
Not established
It does not establish how many accounts were supplied or who the account holders are.
Evidence card B14
OriginalAnybody have [UAE bank A] Business or [UAE bank B] Business in Dubai [...] 50k-150k USD Work. *face to face* • Sim Card • Debit Card • Emirates ID (Phone number & account holder) • Bank logs • Email

Note. The same text ran in another channel on 4 May; Russian-language drop-handler adverts named the same two banks on 22 Jun.

Held
A buyer sought UAE business bank accounts with the holder's SIM, debit card, Emirates ID and online-banking access for USD 50k-150k in transfers.
Not established
It does not establish that any account was handed over.
Evidence card B15
OriginalНужны дроповоды под физ банки [UAE bank A], [UAE bank B] UAE. Отличные условия по работе.
TranslationNeed drop handlers for personal accounts at [UAE bank A] and [UAE bank B], UAE. Excellent working conditions.

Note. Two further adverts (Jul, Aug) offered UAE drops able to register merchants, bank accounts and exchange accounts.

Held
A Russian-language forum post recruited handlers of money-mule personal accounts at two named UAE banks.
Not established
It does not establish that mule accounts at these banks exist or are in use.

Card cash-out also targets UAE payment infrastructure. A November forum post claimed control of card-present terminals in Dubai and sought foreign card dumps (copied magnetic-stripe data) to run through them, saying it avoids Gulf-issued cards (B17). Telegram posts recruited "shooters" to push stolen cards through UAE payment links. Recorded Future reported that a Chinese-speaking fraud group, Tajin, used merchant accounts and payment links at UAE gateways denominated in dirhams, and assessed it "possible" that the group impersonated legitimate UAE businesses [S34].

Evidence card B17
Originali have POS in Dubai and Oman working with swiping cards "white cards" [...] i need cards or dumps from Europe and USA or Africa and worldwide no problem [...]

Note. The poster says it avoids Gulf-issued cards, which points the risk at merchant acquiring and foreign issuers rather than local cardholders.

Held
A forum user claimed control of card-present POS terminals in Dubai and sought foreign card dumps to cash out through them.
Not established
It does not establish that the terminals exist or which acquirer serves them.

Regional context: crypto fraud. A separate October post recruited traffic suppliers for a crypto approval drainer aimed broadly at Middle East merchants and individuals who accept crypto (B18). It does not establish UAE targeting or bank-card cash-out.

Evidence card B18
OriginalWe need people who know how to generate traffic for multichain approval USDT drainer [...] Traffic is needed in the direction of invoices (crypto checks), we mainly need small entrepreneurs and individuals who accept payments in cryptocurrency; rich countries of the Middle East

Note. Reposted on a second forum the same day.

Held
An operator recruited traffic suppliers for a crypto approval drainer aimed at Middle East merchants and individuals who accept crypto.
Not established
It does not establish any UAE victims or losses.

8.2 Card material in posts: a narrow view

Scope of the card figures

These figures cover only payment cards that appeared in clear text in the dark-web posts collected for this report. Brandefense detects stolen cards through many other methods that are not covered here. The figures are not a measure of card theft or fraud loss.

We counted 631 distinct UAE-associated cards in clear text in collected posts [S6]. Of these, 504 were attributed in the post to one of 14 named UAE issuers and 127 carried only a UAE country label. The two most frequent issuers account for 281 of the 504. Most appear in card-checker bot output from February and March. Because August and October were sampled and September was not read, the count is a lower bound. The report publishes issuer-level counts only.

8.3 Identity, KYC and SIM services

Residence-card KYC is a steady market. Buyers offered 5-40 USD per crypto-exchange or fintech account verified with a UAE residence card (B16). Sets of UAE ID and passport images with selfies were offered for 2.5-10 USD. Virtual or Telegram-registered +971 numbers sold for about 1.5 USD. These services connect directly to account-opening fraud and to the mule accounts in §8.1.

Evidence card B16
OriginalWtb [crypto exchange] United Arab Emirates [...] Price : 40$ Escrow++ You need just Residence card تحتاج فقط بطاقة الإقامة للثوثيق

Note. UAE residence-card KYC was in steady demand across exchanges and fintech apps; quoted prices ran from $5 to $40 per account.

Held
A buyer offered $40 per crypto-exchange account verified with a UAE residence card.
Not established
It does not establish how many accounts were bought or which residents took part.
Evidence card B19
Original750k Forex/Crypto Database From UAE For Use ●Recovery ●Depositors ●High Investors [...] Sample: Email Name Phone Country Assigned To Account Status Brand Name Original Retention Owner FTD Currency Total Deposited In USD

Note. The column names look like a broker call-centre CRM; "recovery" lists are used to target people who have already lost money.

Held
A seller listed 750,000 forex and crypto depositor records described as from the UAE, with deposit amounts, for use in recovery scams.
Not established
It does not establish the source brokers or that the depositors live in the UAE.

Leads lists are the input to call-centre fraud. A seller listed 750,000 forex and crypto depositor records described as UAE-linked, with deposit amounts, explicitly for "recovery" scams that target people who have already lost money (B19).

8.4 Prices in context

Item (UAE-related, as advertised)PriceCard
Insurer customer file, 80,000 records200 USDB01
Developer customer and identity-document data100 USDB02
Super-administrator access to a government web system800 USDB08
Transport-authority dataset, 50GB claimed5,000 USDB03
Exchange account verified with a UAE residence card5-40 USDB16
UAE ID or passport image set with selfie2.5-10 USDn/a
Virtual +971 numberabout 1.5 USDn/a

Prices are asking prices in posts. They say nothing about whether a sale happened or whether the goods were genuine, and sellers inflate and recycle.

8.5 Official and vendor warnings

Official and vendor warnings described the same patterns from the victim's side.

DateBodyWhat was reportedSource
2026-03-02Dubai PoliceCallers posing as crisis-management staff seek UAE PASS and Emirates ID data for SIM swaps and banking-app takeover[S49]
2026-03-09DFSA (Dubai Financial Services Authority)Firms impersonating authorised firms and cloned public-register domains[S53]
2026-03-10Netcraft (vendor)Hundreds of "AE GOV" e-mails with the interior ministry's logo, sent from 4 March, pushed a fake registration form. A lookalike customs parcel site asked for a 20 AED fee[S61]
2026-04-11Dubai PoliceRise in fake calls and SMS posing as officials and bank staff seeking passwords and one-time codes[S47]
2026-04-11Public ProsecutionA network sent fake toll and fine SMS, some for 4 AED, to harvest card data. 35 reports, arrests including one local suspect, 22 card terminals seized[S62]
2026-04-17Unit 42 (vendor)Fake payment pages using postal-service themes, and fake fine-payment flows impersonating Dubai authorities, collected card data[S64]
2026-04-25Abu Dhabi PoliceFake social-media accounts selling tickets, visa services, vehicles and investments, and requesting data under parcel-delivery pretexts[S50]
2026-04-29Dubai Police276 arrests and nine fraud centres dismantled with US and Chinese police[S45]
2026-04-30ICP (the federal identity and citizenship authority)Calls and websites used its name and logo to obtain personal data. ICP warned never to share one-time passwords or digital-identity codes[S63]
2026-07-05Sharjah PoliceSeven arrested for impersonating officials and getting victims to install apps that gave access to their phones; bank accounts opened in other people's names[S51]
2026-07-07Dubai PoliceFake consumer-protection sites followed by calls pushing remote-access software during online banking[S48]
2026-10-22Ministry of InteriorMore than 960 arrests and 4,126 bank accounts blocked in a 30-country operation, 1 July-30 September[S46]
2026-10-23Dubai PoliceSix arrested over a fake shopping site that harvested card data[S52]

Reading across both views. The posts and the police reports describe the same chain: identity data and residence cards feed account opening, mule accounts move money, and remote-access tools and fake officials take over victims' sessions. The central bank's refund duty for SMS-only fraud (§10.3) shifts part of that cost onto institutions.

Key takeaways

  1. 01

    Verified UAE accounts tied to an Emirates ID or residence card are the core fraud commodity.

  2. 02

    Payment links and card-present terminals are cash-out channels; monitor merchants, not only cardholders.

  3. 03

    Police warnings and dark-web posts describe the same chain: identity data, mule accounts and remote-access takeover.

Chapter 9

Banking and finance deep dive

This chapter answers

Where does the visible exposure of UAE banks sit, and which of it points to intrusion rather than to customer fraud?

12 of 23banks in our list with a credential listed for sale on the day of the check

In short

All 23 banks in our list have infected devices associated with their domains, but 98% of those devices are outside the employee classification, and their ownership remains unverified. All 23 bank domains publish an enforcing DMARC policy. Twelve had a current credential listing, and posts name UAE banks in mule recruitment and card-checker output. Triage the listings and the 543 employee-classified devices first, then harden account opening and recovery.

This chapter uses aggregates only. The 23 banks are the central-bank-licensed banks in the 250-organisation list, including two foreign banks' UAE operations and one development bank. Payment firms, exchanges and investment bodies are in the wider banking and finance sector (Chapter 3).

24,526

infected devices associated with the 23 banks' domains (543 employee-classified)

71,616

credential records: breach databases, stealer logs and combolists

23 of 23

banks enforcing DMARC (22 reject, 1 quarantine)

9.1 Where the exposure sits

Measure (23 banks)Value
Banks with infected-device associations23
Banks with employee-classified devices19
Device associations, all / employee-classified24,526 / 543
Share of devices (not credentials) at the two largest banks47% (71% at the largest five)
Credential records71,616 (44,709 breach-database, 7,335 stealer-log, 19,572 combolist)
Banks with a current credential listing12

Most associations are outside the employee classification; ownership remains unverified. 23,983 of 24,526 bank-associated devices are not employee-classified. Many may be customers' own computers, but ownership is not established. For a bank they are a fraud signal (session theft, account takeover and recovery abuse), and they cannot be ruled out as an intrusion route. The 543 employee-classified devices are the first priority for intrusion triage.

Concentration is moderate. Two banks carry nearly half of the device associations.

9.2 What posts say about UAE banks

  • Mule accounts. Posts sought business and personal accounts at named UAE banks with the holder's SIM, card and Emirates ID (B14, B15), and remittance and wallet accounts tied to an Emirates ID (B13).
  • Card material. 504 of the 631 cards seen in clear text in collected posts were attributed to one of 14 UAE issuers, mostly in card-checker output in February and March (§8.2, with its scope note).
  • Cash-out infrastructure. A forum user claimed card-present terminals in Dubai for cash-out of foreign cards (B17), and channels recruited people to push stolen cards through UAE payment links.
  • Credential lines. Automated uploads carried online-banking login lines for UAE retail banks, which usually come from infected customer devices.

9.3 What the regulator changed

The central bank's May direction, its planned Anti-Fraud Operations Centre and the refund duty for SMS-only fraud (§10.3) aim at the same chain [S36][S38]. That is the customer-side chain the posts describe. For a bank, the cost of a weak approval method now falls on the bank. Since 14 September the central bank's operational-risk regulation also covers central-bank-licensed financial institutions, not only banks. It requires notice within four hours of an event that has, or is likely to have, a significant impact on critical operations, and independent penetration tests of critical functions [S57].

9.4 What banks should do

  1. Contain privileged, remote-access or no-MFA accounts the same day; validate other current listings within five working days and employee devices within 30 days. They are the most direct intrusion signals in this chapter (§12.1 rows 2-3).
  2. Treat the other device associations as fraud intelligence too. Feed them into session-risk scoring and step-up authentication, and escalate any linked to staff or administrative access (§12.1 row 11).
  3. Harden account opening against residence-card KYC and mule recruitment. Test with synthetic cases; watch for accounts that receive many small inbound transfers and pay out quickly (§12.1 row 18).
  4. Watch merchants as well as cardholders. Payment links and terminals are cash-out channels (§8.1; §12.1 row 19).

Key takeaways

  1. 01

    Most bank-associated devices are outside the employee classification, and their ownership is unverified; triage the 543 employee-classified devices and 12 current listings first.

  2. 02

    All assessed bank domains publish an enforcing DMARC policy; keep testing email authentication and defences against phishing from hijacked mailboxes.

  3. 03

    Mule accounts, residence-card KYC and payment-link cash-out are the fraud chain to break.

Chapter 10

Regulatory and national response

This chapter answers

Which rules and official measures changed for UAE organisations in 2026, and what should a CISO do about them now?

4 hfor central-bank-licensed financial institutions to notify the central bank of a significant operational event, under a regulation in force since 14 September 2026

In short

The UAE's cyber rules are layered: federal law, emirate-level standards and the separate regimes of the two financial free zones. The clearest 2026 changes came from the central bank: a four-hour incident-notification rule for central-bank-licensed financial institutions, and a push beyond SMS one-time passwords with refund duties for SMS-only fraud. Map which regime applies to each entity, then rehearse breach notification against the shortest clock.

This chapter is not legal advice. We list only provisions we read in an official text or in a named secondary source; where we could not retrieve an official text, we say so.

10.1 Who sets the rules

LayerBodyWhat it covers
Federal policyUAE Cybersecurity CouncilNational strategy, policies and incident coordination [S54][S43]
Federal bankingCentral Bank of the UAE (CBUAE)Licensed banks, insurers and payment firms [S36][S42]
Federal data and digital governmentFederal Authority for Artificial Intelligence and Data (announced 14 June 2026)AI oversight, digital government and data regulation, per a law-firm analysis [S41]
Emirate (Dubai)Dubai Electronic Security Center (DESC)Dubai government and semi-government entities [S44]
Financial free zoneDIFC Commissioner of Data ProtectionFirms in the Dubai International Financial Centre [S39]
Financial free zoneADGM Office of Data ProtectionFirms in Abu Dhabi Global Market [S40]

10.2 What the texts say

InstrumentProvision we readSource
DIFC Data Protection Law No. 5 of 2020, as amended (incl. Amendment Law No. 1 of 2025)Article 41: notify the Commissioner of a personal-data breach "as soon as practicable in the circumstances"; Article 42: notify data subjects of high-risk breaches; Schedule 2: a fine of up to 50,000 USD for failing to report under either article[S39]
ADGM Data Protection Regulations 2021Article 32: notify the Office of Data Protection without undue delay and, where feasible, not later than 72 hours after becoming aware[S40]
Federal Decree-Law No. 34 of 2021 on countering rumours and cybercrimesArticle 2: hacking a system, imprisonment and/or a fine of 100,000-300,000 AED, rising where data is acquired or damage results; Article 3: government systems, temporary imprisonment and a fine of 200,000-500,000 AED, at least 5 years where damage or a cyberattack is involved; Article 5: harm to government or critical-facility systems, temporary imprisonment and a fine of 500,000-3,000,000 AED, with a cyberattack an aggravating circumstance; Article 40: internet fraud, at least one year and/or 250,000-1,000,000 AED. In force since 2 January 2022[S56]
CBUAE Operational Risk Management Regulation No. C 1/2026 (in force 14 September 2026)Applies to central-bank-licensed financial institutions, not only banks (press report of the regulation). Notify the central bank within 4 hours of an event that has, or is likely to have, a significant impact on critical operations; a brief report within 24 hours; notification within 72 hours of any high-severity incident; independent external penetration tests for critical functions[S57]
Federal Decree-Law No. 45 of 2021 (PDPL)In force; implementing regulations still not issued and no private-sector supervisory authority clearly designated as of June 2026, per a law-firm analysis[S41]
Federal Decree-Law No. 6 of 2025 (central bank law)Article 149, as summarised by a practice guide: fraud prevention and detection, and prompt reporting of verified fraud and security breaches to the central bank[S42]
Dubai Information Security RegulationIssued under Resolution No. 13 of 2012 and maintained under Dubai Law No. 11 of 2014, with further DESC standards for IoT and other areas[S44]
National Cybersecurity StrategyApproved by the Cabinet on 3 February 2025; five pillars[S43]

We read Federal Decree-Law No. 34 of 2021 in an English text hosted by ADGM; the official portal could not be retrieved, and later amendments were not checked. We could not retrieve the official PDPL text, so we do not quote its notification wording.

10.3 The central bank's authentication shift

Banks are moving card and login approval from SMS codes to their apps. Several major banks stopped sending SMS one-time passwords for online card purchases from 6 January 2026 and moved approval into the bank's app [S37]. On 21 May the central bank told licensed institutions to strengthen anti-fraud consumer protection and reduce reliance on single-factor verification such as SMS one-time passwords. It also said it had begun setting up a central Anti-Fraud Operations Centre for real-time fraud monitoring; no deadline was published [S36].

In July, Emarat Al Youm reported a central-bank disclosure on SMS-only fraud. Institutions must refund the full amount where fraud used a one-time password sent only by SMS, once the customer reports it promptly and the report is verified [S38]. For banks, that moves the cost of weak authentication onto the institution.

10.4 What the police and the Council did

Enforcement in 2026 targeted fraud at scale. Dubai Police reported 276 arrests and nine fraud centres dismantled in a joint operation with US and Chinese police announced on 29 April [S45]. The Ministry of Interior reported more than 960 arrests and 4,126 bank accounts blocked in a 30-country operation from 1 July to 30 September [S46]. The Council issued public advisories, including a wiper-malware warning on 4 April [S11].

10.5 What CISOs should do now

  1. Map each legal entity to its regime. A group with a DIFC subsidiary, an ADGM fund and an onshore bank faces three breach-notification rules. Keep the map in the incident plan (§12.1 row 12).
  2. Rehearse against the shortest clock. For central-bank-licensed financial institutions that is now four hours to the regulator [S57]. Elsewhere use ADGM's 72-hour outer limit where it applies, and "as soon as practicable" in the DIFC (§12.1 row 12).
  3. Finish the move off SMS codes. For banks and payment firms, the central bank's direction and the refund duty make SMS-only approval a direct cost [S36][S38] (§12.1 row 10).
  4. Track the PDPL regulations. Prepare data inventories and breach logs now; the implementing rules may arrive with the new federal authority [S41] (§12.1 row 13).

Key takeaways

  1. 01

    Central-bank-licensed financial institutions now face a four-hour notification clock, and DIFC and ADGM entities have their own rules; map them before an incident.

  2. 02

    The central bank's authentication direction and refund duty make SMS-only codes a liability.

  3. 03

    Federal data-protection rules are still awaiting implementing regulations; prepare inventories now.

Chapter 11

Outlook

This chapter answers

What should UAE organisations plan for in 2027, how confident are we, and what would change the plan?

3conditional scenarios, each with the signal that would change it

In short

Our judgements are about exposure and claims, not about intentions of states. Identity exposure and account fraud are likely to persist whatever happens regionally. Observed destructive and hacktivist claims clustered in the March-April 2026 heightened period, and our coverage is incomplete; plan for recurrence if similar conditions return. Plan for both: keep listing and device triage running all year, and keep wiper recovery and DDoS readiness tested for the next heightened period.

11.1 Key judgements

JudgementConfidenceBasisLimit
Credential and infected-device exposure will remain the most common measured exposure for leading UAE organisationsHighChapter 3 counts; the year-round KYC and account trade (Chapter 8)Association counts, not verified compromise
Hacktivist DDoS and destructive claims will cluster around periods of regional tensionMedium2026 pattern: claims concentrated in March-April (Chapter 6); official statements on the heightened period [S22]One year of data; claimants change names; September posts not available
Real-estate customer data will remain the most frequently advertised UAE-specific dataset; insurance and transport will see recurring single-organisation claimsMediumChapter 4 cases; at least nine real-estate sellers; buyer demand preceding supplySellers recycle; claims unverified
Ransomware listings of UAE firms will stay well above Gulf comparatorsMedium84 listings to 20 November against 7-30 for comparators [S5]Listings are claims and include mislabels
Payment-authentication changes will shift fraud toward mule accounts, remote-access takeover and payment linksMediumCentral-bank direction and refund duty (§10.3); police warnings (§8.5)Fraud-loss data is not public

11.2 What would change the assessment

  • A confirmed destructive incident at a named state body or critical operator would move destructive risk from a claim-driven to an evidenced judgement and justify stronger recovery investment across sectors.
  • A sustained fall in current credential listings across the 250 organisations at a repeat check would be an observation to interpret, not proof that controls work. Listings also move with market supply, seller behaviour and coverage. Response is better measured by validated-account dispositions, response times, session-revocation evidence and recurrence among remediated accounts.
  • Publication of the PDPL implementing regulations would create a breach-notification baseline and more public incident data.
  • A vendor or official report tying a leak-site listing to a confirmed UAE incident would let us calibrate how many listings reflect real intrusions.

11.3 Conditional scenarios

These are planning assumptions, not forecasts.

  1. Renewed regional tension. If official statements again report a heightened period, expect DDoS claims against federal and emirate portals within days, relayed hack-and-leak claims against energy, ports and aviation, and wiper attempts. Signal: hacktivist channels publishing UAE target lists.
  2. Steady state. If no heightened period occurs, expect the fraud economy to dominate: account trading, residence-card KYC, real-estate leads and ransomware listings at the 2026 pace. Signal: listing and KYC prices staying low.
  3. Authentication gap closes. If banks finish moving approval into apps, expect a shift to remote-access scams and payment-link cash-out rather than SMS-code theft. Signal: police warnings focusing on remote-access apps.

Key takeaways

  1. 01

    Identity exposure and account fraud are likely to persist regardless of regional events.

  2. 02

    Observed destructive claims clustered during the heightened period; plan for recurrence if similar conditions return.

  3. 03

    Watch for confirmed incidents behind listings; they would show how far listings reflect real intrusions.

Chapter 12

Action plan

This chapter answers

What should each team do in the next 90 days, and how will the board know it was done?

20actions with a trigger, an owner and completion evidence

In short

Start by confirming you receive credential-listing and infected-device alerts, then act on what is specific to you: current listings, employee devices and internet-facing systems. Then close the authentication, email and backup gaps, rehearse wiper, DDoS and identity-fraud scenarios, and report each row's completion evidence to the board.

12.1 30/60/90 days

This is a sequence, not a waiting period. A current material threat should enter your incident process immediately; the trigger column says when a row starts again.

RowWhenTriggerActionOwnerCompletion evidence
1Days 1-30Start of the planConfirm that you receive credential-listing and infected-device alerts for your primary domains; if not, arrange themCISO and threat intelligenceAlert source named; first alert received
2Days 1-30Each new credential-listing alertValidate the account and its MFA status. Contain privileged, remote-access or no-MFA accounts the same day; record a disposition for the rest within 5 working daysIdentity teamEach listing has a disposition: reset, already remediated, or not ours
3Days 1-30Each new employee-device alertValidate employee-classified device associations; revoke sessions and tokens where activeIdentity and endpoint teamsDevice list reconciled with asset inventory; revocations logged
4Days 1-30Start of the plan; each new edge-system advisoryInventory internet-facing VPN, mail, CRM, CMS and AI-orchestration endpoints; patch or isolate end-of-life systems; enforce single sign-on and MFA on CMS and administrator interfaces and remove local administrator accountsInfrastructureExternal re-test passes; exceptions signed off
5Days 1-30Start of the plan; each new camera advisoryPatch or remove internet exposure of IP cameras and recorders, including CVE-2017-7921 and CVE-2021-33044, using the affected and fixed firmware by model in §7.2Facilities and infrastructureCamera inventory; external re-test shows no exposed management interfaces
6Days 1-30Start of the plan; each wiper advisoryRestore a critical system from offline backup within the promised recovery timeInfrastructure and business continuityTimed restore record
7Days 31-60Start of the planAlert on new remote-management tools, DLL side-loading from user-writable paths and unusual outbound connections from CRM and mail serversSOCDetection live; test alert fired
8Days 31-60Start of the planEnforce DMARC reject or quarantine on every sending domainEmail and DNS ownersDMARC policy per domain
9Days 31-60Start of the plan; renew when the Council or police announce a heightened periodContract upstream DDoS mitigation for public portalsInfrastructure and networkMitigation contract in place; failover tested
10Days 31-60Start of the planMove remaining customer and staff approvals off SMS one-time codesDigital channels and fraudShare of approvals by method, before and after
11Days 31-60Each new customer-device alert (banks and payment firms)Feed non-employee device associations into session-risk scoring and step-up authenticationFraud and digital channelsSignal live in risk scoring; first review
12Days 31-60Start of the plan; any new legal entity or ruleMap each legal entity to its notification regime (central bank four-hour rule, onshore, DIFC, ADGM) and rehearse against the shortest clockLegal and privacyMap in the incident plan; drill timings
13Days 31-60Start of the plan; update when the PDPL implementing regulations are issuedPrepare data inventories and breach logs; update the notification mapPrivacyInventory and breach log in place; map updated
14Days 31-60Start of the plan; each new data-sale claim naming youReview CRM and loyalty-platform exports and partner accessData ownersExport log review signed off
15Days 61-90, or at once when triggeredA data-sale or leak claim naming your customers, once a sample or field list is assessed as credible, or a confirmed incidentWarn customers about impersonation using leaked property, policy or loyalty data, as an awareness notice that does not confirm a breachCustomer communicationsNotice published
16Days 61-90Start of the plan; each claim naming youRehearse a hacktivist DDoS and leak claim, including who confirms status publicly; verify each real claim against telemetry and the system ownerCommunications and SOCExercise report with timings
17Days 61-90Start of the plan; each wiper advisoryRehearse a wiper scenario across IT and OTCISO and OT ownersExercise report; gaps assigned
18Days 61-90Start of the plan; new KYC or SIM-swap pattern in warningsTest account-opening and recovery against residence-card and SIM-swap fraud with synthetic cases; telecoms tighten SIM-swap and number-port checksFraud and identityTest results; controls changed
19Days 61-90Start of the planMonitor merchants and payment links for cash-out patternsAcquiring and fraudRules live; first review
20Days 61-90Day 90, then each quarterReport validated-account dispositions, response times, session revocations and recurrence among remediated accounts; show listing and device counts as context onlyCISOBoard paper with response measures and before-and-after context

12.2 By role

  • Boards and executives. Ask for the listing disposition rate and the timed backup restore. Both are measurable within 30 days.
  • CISOs. Treat a current credential listing as an incident trigger; fund wiper recovery and upstream DDoS mitigation before the next heightened period.
  • SOC and threat intelligence. Hunt side-loaded DLLs, remote-management tools and unusual outbound traffic from mail and CRM servers; verify every hacktivist claim against telemetry before escalation.
  • Fraud teams. Focus on account opening, recovery, mule accounts and payment links; SMS codes are no longer a defensible single factor.
  • Communications and legal. Prepare holding statements for unverified claims; keep the notification map current.

12.3 How Brandefense can help

Brandefense combines Cyber Threat Intelligence, Digital Risk Protection and External Attack Surface Management. The analysis in this report used the same data and scoring that the platform applies to monitored organisations: infected-device and credential associations, current credential-market listings, lookalike domains, exposed documents and dark-web mentions. It does not promise that every claim can be verified or that a historical record remains usable.

Bring your domains, brands and security priorities to a 30-45 minute demo with Sales and Presales. The team can show how platform monitoring relates external signals to the assets you manage. A Brandefense team member or a partner in your region will follow up.

Request a demo

Key takeaways

  1. 01

    Start with alerts, listings and employee devices; they are specific and measurable.

  2. 02

    Test backup restores and DDoS readiness before the next heightened period.

  3. 03

    Measure progress by completion evidence, not by plans.

Appendix A. Method

A.1 Window, sources and priority

The research window is 1 January-20 November 2026 by the date a post was published, not the date it was collected. Own data comes first: Brandefense Blackhole (dark-web and messaging posts, infected-device and credential associations, card material in posts), Ransompedia (ransomware leak-site listings) and Brandefense Atlas exposure ratings. External sources give context and are cited only after the supporting passage was read. Data were extracted on 21 November 2026. Sources S1-S6 are Brandefense's own data and have no public address; every external source in Appendix C carries a link and the date it was verified.

A.2 Blackhole posts

ItemValue
Posts with the UAE country tag130,477 counted
CoverageRelevant-post ranges for January-July and November; August and October covered only in part; September posts not available
Forum postsForum posts mentioning the UAE; 1,271 distinct posts
Relevant (cleaned) posts, January-July and November23,663-24,456 of 65,544, given as a range

Of 30 random relevant posts, 27 were crime-related and 10 named the UAE specifically, so cleaned counts are an upper bound for UAE-specific criminal activity.

Two limits shape every trend in this report. Family counts are not compared across June 2026. September posts were not available; September appears only in monthly counts and in the forum posts mentioning the UAE.

A.3 The 250 organisations

Selection, verification and limits are in §3.1. For each primary domain we read the exposure signals that Atlas uses for its ratings. They are infected devices, employee devices, credential records, dark-chat and dark-web mentions, new lookalike domains, documents that reference the domain, and current and past credential-market listings. Data were read on 21 November 2026.

A.4 Atlas ratings

Each organisation received an Atlas exposure rating from these signals. The national headline is reported as Atlas gives it; sector results are given as signal counts. Treat a current credential-market listing as a reason to validate accounts, not as proof of a breach.

205 organisations had candidate lookalike matches; those matches were not all validated.

A.5 DNS, TLS and web checks

We checked public DNS records for mail, email authentication and DNSSEC, and checked TLS and the homepage of each domain. Missing, invalid and monitoring-only (p=none) DMARC policies count as no enforcement. No scanning went beyond these passive checks. The passive hygiene index is an Odin analytical composite of these checks on a scale of 0-100; a higher value means weaker hygiene. It is a model, not an Atlas rating. A sector value is the index's summary for that sector, not an average of its organisations.

A.6 Card material in posts

Scope: only payment cards that appeared in clear text in the dark-web posts collected for this report. Brandefense detects stolen cards through many other methods, which are outside this report. These figures do not measure card theft or fraud loss. The report publishes issuer-level counts only.

A.7 Ransomware

We used Ransompedia accepted listings for the UAE, Saudi Arabia, Qatar, Kuwait and Oman, all dates, dated by publication. Rejected and duplicate listings are excluded. A public tracker and relayed Blackhole posts are used only as cross-checks.

A.8 Incident coverage

Incident coverage draws on our post data for the 250 organisations, public reporting in English, Arabic and Russian, and official UAE pages for the window, with a final check to 20 November 2026.

Remaining coverage limits. Our view is partial:

  • Public reporting was not equally deep for every organisation.
  • For some official texts, including federal legislation and the central bank's rulebook, we relied on copies hosted elsewhere or on named secondary sources, as cited.
  • Tor ransomware leak sites are covered only through Ransompedia.
  • Closed forums, private groups and sales arranged in direct messages are outside our collection.
  • Incidents that organisations handle without disclosure stay invisible.

That an incident is absent from this report does not mean it did not happen.

A.9 Confidence and boundaries

High confidence applies to a reproducible measurement, not to a criminal's underlying assertion. Medium indicates an interpretation with a clear supporting line and stated limits. "Unverified" means not independently established; it is neither proof of fabrication nor proof of a breach. Victim organisations are described by role; a body or company is named only where the incident was officially confirmed and widely reported. Attributions to states are reported only as the source states them; the authors make none. Actor aliases are printed; links, contacts, indicators and personal data are withheld.

Appendix B. Evidence register

Every post quoted in this report appears as a redacted post card in the chapter shown. Excerpts are short; omissions are marked [...]; identifiers, contacts, links and victim organisations are replaced with labels in brackets, under the policy in A.9. Political and religious statements in actor posts are left out. Translations are ours unless the post carried the actor's own English. Posting dates are not intrusion dates.

CardPostedVenueAlias as shownLanguageShown in
B012026-01-30Breach forumInsurer-data seller (alias withheld)English§4.6
B022026-04-02Breach forumSeller of B01 (alias withheld)English§4.4
B032026-11-15Breach forumdatabreach000English§4.6
B042026-04-13Breach forumksa901English§4.4
B052026-09-10Leak aggregator forumAggregator account (actor handle withheld)English§6.3
B062026-05-06Breach forumattackercompanyEnglish§4.4
B072026-01-26Breach forumRetrogadeEnglish§4.5
B082026-04-26Breach forumCrimsonEnglish§4.5
B092026-03-23Breach forumrSosaEnglish§4.5
B102026-02-24Breach forumTheAshbornEnglish§4.5
B112026-03-05Breach forumCVDEADEnglish§4.5
B122026-08-11Leak aggregator forumX Forum BotEnglish§4.5
B132026-02-09Telegram channelAnonymous posterEnglish§8.1
B142026-06-04Telegram channelAnonymous posterEnglish§8.1
B152026-06-22Carding/fraud forumSOQARussian§8.1
B162026-02-24Telegram channelAnonymous posterEnglish, Arabic§8.3
B172026-11-17Carding/fraud forumz3fraanEnglish§8.1
B182026-10-05Carding/fraud forumMoon_7thShiftEnglish§8.1
B192026-10-29Carding/fraud forumRummRifEnglish§8.3
B202026-02-18Breach forumAnonymous buyerEnglish§4.4
B212026-03-02Actor channel313 TeamArabic, English§6.2
B222026-03-12Actor channelKeymous+English§6.2
B232026-03-27Breach forumcoderxEnglish§6.3
B242026-06-01Actor channelGolden FalconEnglish§6.3

Appendix C. Sources

  1. S1Brandefense Blackhole post corpus, UAE country tag and forum posts mentioning the UAE, post dates 1 January-20 November 2026, extracted 21 November 2026.
  2. S2Brandefense Blackhole infected-device, breach-database, stealer-log and combolist associations for 250 domains, read 21 November 2026.
  3. S3Brandefense Atlas exposure ratings for the 250 domains, 21 November 2026, including credential-market listings, lookalike domains, exposed documents and mentions.
  4. S4Brandefense public DNS, TLS and homepage checks of the 250 domains, 21 November 2026.
  5. S5Brandefense Ransompedia, accepted listings for the UAE, Saudi Arabia, Qatar, Kuwait and Oman, all dates, extracted 21 November 2026.
  6. S6Brandefense Blackhole extraction of UAE-associated cards seen in clear text in collected posts, 21 November 2026.
  7. S7ransomware.live, country victims for the UAE, accessed 21 November 2026 (cross-check only). https://www.ransomware.live/ (article URL withheld). Verified on 21 November 2026.
  8. S8DataReportal, "Digital 2026: the United Arab Emirates". https://datareportal.com/reports/digital-2026-united-arab-emirates. Verified on 21 November 2026.
  9. S9Khaleej Times (WAM), "Over 70% of cyber threats targeting UAE are state-sponsored, authority says", 18 February 2026. https://www.khaleejtimes.com/uae/over-70-of-cyber-threats-targeting-uae-are-state-sponsored-authority-says. Verified on 21 November 2026.
  10. S10The National, "UAE foils AI-powered 'terrorist cyber attacks' on vital sectors", 22 February 2026. https://www.thenationalnews.com/news/uae/2026/02/22/uae-foils-ai-powered-terrorist-cyberattacks-on-vital-sectors. Verified on 21 November 2026.
  11. S11UAE Cybersecurity Council, advisory "Wiper Malware Campaign Targeting Multiple Sectors" (TLP:WHITE), 4 April 2026, hosted by ADGM. https://assets.adgm.com/download/assets/432318719+-+Wiper+Malware+Campaign+Targeting+Multiple+Sectors.pdf/af059afe318811f1b18b0634db0fb850. Verified on 21 November 2026.
  12. S12Gulf News, "UAE Cyber Security Council warns against wiper malware threat", updated 19 March 2026. https://gulfnews.com/uae/uae-cyber-security-council-warns-against-wiper-malware-threat-1.500480274. Verified on 21 November 2026.
  13. S13Khaleej Times, report on remarks by the head of the UAE Cybersecurity Council at the SAMENA summit, 1 April 2026. https://www.khaleejtimes.com/business/uae-cyberattacks-triple-to-600000-amid-iran-conflict-says-cybersecurity-chief. Verified on 21 November 2026.
  14. S14Emarat Al Youm, report on remarks by the head of the UAE Cybersecurity Council in Fujairah (Arabic), 20 April 2026. https://www.emaratalyoum.com/local-section/other/2026-04-20-1.2037698. Verified on 21 November 2026.
  15. S15Khaleej Times (WAM), "UAE authority foils sophisticated cyberattacks on entities in financial sector", 3 July 2026. https://www.khaleejtimes.com/uae/foils-cyberattacks-entities-financial-sector. Verified on 21 November 2026.
  16. S16Gulf News (WAM), "UAE foils advanced cyberattacks targeting vital sectors", 10 August 2026. https://gulfnews.com/amp/story/uae%2Fuae-foils-advanced-cyberattacks-targeting-vital-sectors-1.500636064. Verified on 21 November 2026.
  17. S17Khaleej Times, "$5 million ransom: UAE official recalls how country responded to major cyberattack", 15 September 2026 (updated 16 September). https://www.khaleejtimes.com/uae/records-640000-cyberattacks-a-day-chief-reveals. Verified on 21 November 2026.
  18. S18The National, report of a CNN interview with the head of the UAE Cybersecurity Council, 16 September 2026. https://www.thenationalnews.com/news/uae/2026/09/16/irans-irgc-behind-many-cyberattacks-on-uae-says-security-chief/. Verified on 21 November 2026.
  19. S19Euronews, interview with the head of the UAE Cybersecurity Council at the Arab Media Summit, 17 September 2026. https://www.euronews.com/2026/09/17/every-iranian-strike-came-with-a-cyberattack-uae-cyber-chief-says. Verified on 21 November 2026.
  20. S20Khaleej Times (WAM), "UAE foils around 750,000 cyberattacks targeting sectors including energy, education", 21 October 2026. https://www.khaleejtimes.com/uae/thwarts-750000-cyberattack-attempts. Verified on 21 November 2026.
  21. S21Emarat Al Youm, report on remarks by the head of the UAE Cybersecurity Council at Dubai Municipality's cyber security week (Arabic), 28 October 2026. https://www.emaratalyoum.com/local-section/other/2026-10-28-1.2096890. Verified on 21 November 2026.
  22. S22Khaleej Times, "Over 40 cyber groups tried to attack UAE infrastructure amid regional crisis, official says", 18 November 2026. https://www.khaleejtimes.com/uae/over-40-cyber-groups-tried-to-attack-uae-infrastructure-amid-regional-crisis-official-says. Verified on 21 November 2026.
  23. S23Emarat Al Youm, report on remarks by the head of the UAE Cybersecurity Council at the World Police Summit (Arabic), 19 November 2026. https://emaratalyoum.com/local-section/accidents/2026-11-19-1.2104340. Verified on 21 November 2026.
  24. S24The National, "UAE's Landmark Group probes data breach in Shukran loyalty programme", 11 November 2026. https://www.thenationalnews.com/business/money/2026/11/11/uaes-landmark-group-probes-data-breach-for-its-shukran-loyalty-programme/. Verified on 21 November 2026.
  25. S25Khaleej Times, "Shukran members' personal data accessed in data breach, but card details safe", 11 November 2026. https://www.khaleejtimes.com/business/shukran-members-personal-data-accessed-in-data-breach-but-card-details-safe. Verified on 21 November 2026.
  26. S26Security Affairs, "Iran-linked group Handala claims to have breached three major UAE organizations", 13 April 2026. https://securityaffairs.com/190716/hacking/iran-linked-group-handala-claims-to-have-breached-three-major-uae-organizations.html. Verified on 21 November 2026.
  27. S27UpGuard news page on a claim against a UAE port operator, May 2026. https://www.upguard.com/ (article URL withheld). Verified on 21 November 2026.
  28. S28Daily Dark Web, report of an alleged claim against a UAE airport operator, 31 March 2026. https://dailydarkweb.net/ (article URL withheld). Verified on 21 November 2026.
  29. S29The National, "Missile attacks and cyber hacks: Dual threats of modern warfare", 2 March 2026. https://www.thenationalnews.com/future/technology/2026/03/02/cyberwar-and-military-escalation-converge-as-middle-east-digital-infrastructure-is-attacked. Verified on 21 November 2026.
  30. S30StormWall, "DDoS Threat Landscape in MENA: Q1 2026 Report" (undated page). https://stormwall.network/resources/blog/q1-2026-ddos-report-mena. Verified on 21 November 2026.
  31. S31Palo Alto Networks Unit 42, "Boggy Serpens threat assessment", 16 March 2026. https://unit42.paloaltonetworks.com/boggy-serpens-threat-assessment/. Verified on 21 November 2026.
  32. S32Palo Alto Networks Unit 42, "Tracking Iranian APT Screening Serpens' 2026 Espionage Campaigns", 22 May 2026. https://unit42.paloaltonetworks.com/tracking-iran-apt-screening-serpens/. Verified on 21 November 2026.
  33. S33ESET, "ESET APT Activity Report Q4 2025-Q1 2026", 28 May 2026. https://www.welivesecurity.com/en/eset-research/eset-apt-activity-report-q4-2025-q1-2026/. Verified on 21 November 2026.
  34. S34Recorded Future Insikt Group, "Inside Tajin Group's Phishing and Money Laundering Network" (undated page; data to July 2026). https://www.recordedfuture.com/research/tajin-group-gurantee-marketplace. Verified on 21 November 2026.
  35. S35Khaleej Times, "91% of UAE DDoS attacks are low-volume as threats turn stealthier", 22 September 2026 (Help AG data). https://www.khaleejtimes.com/business/91-of-uae-ddos-attacks-are-low-volume-as-threats-turn-stealthier. Verified on 21 November 2026.
  36. S36Gulf News, "UAE banks ordered to tighten anti-fraud security beyond OTPs", 21 May 2026. https://gulfnews.com/business/banking/uae-banks-ordered-to-tighten-anti-fraud-security-beyond-otps-1.500548327. Verified on 21 November 2026.
  37. S37Gulf News, "UAE banks to end SMS OTPs for online card payments from January 6", updated 2 January 2026. https://gulfnews.com/business/banking/uae-banks-to-end-sms-otps-for-online-card-payments-from-january-6-1.500396452. Verified on 21 November 2026.
  38. S38Emarat Al Youm, report on a central-bank disclosure on refunds for SMS-only fraud (Arabic), 16 July 2026. https://www.emaratalyoum.com/business/local/2026-07-16-1.2065407. Verified on 21 November 2026.
  39. S39DIFC, Data Protection Law, DIFC Law No. 5 of 2020, as amended (incl. DIFC Laws Amendment Law No. 1 of 2025). https://www.difc.com/business/laws-and-regulations/legal-database/difc-laws/data-protection-law-difc-law-no-5-2020. Amendment law: https://assets.difc.com/v1/media/edge/images/dubaiintern0078-difcexperie96c5-production-3253/media/project/difcexperiences/difc/difcwebsite/documents/laws--regulations/amendment-law-no-1-of-2025.pdf. Verified on 21 November 2026.
  40. S40ADGM Office of Data Protection, "Personal Data Breach Notifications". https://www.adgm.com/operating-in-adgm/office-of-data-protection/data-breach-notifications. Verified on 21 November 2026.
  41. S41Morgan Lewis, "UAE establishes Federal Authority for Artificial Intelligence and Data", June 2026. https://www.morganlewis.com/pubs/2026/06/uae-establishes-federal-authority-for-artificial-intelligence-and-data. Verified on 21 November 2026.
  42. S42Chambers and Partners, "Cybersecurity 2026: UAE, trends and developments" (Ankura authors; undated). https://chambers.com/practice-guides/guides/cybersecurity-2026/uae/trends-and-developments. Verified on 21 November 2026.
  43. S43Government of Dubai Media Office, UAE Cabinet meeting approving the National Cybersecurity Strategy, 3 February 2025. https://mediaoffice.ae/en/news/2025/february/03-02/mohammed-bin-rashid-chairs-cabinet-meeting. Verified on 21 November 2026.
  44. S44Dubai Electronic Security Center, "Standards and policies". https://www.desc.gov.ae/regulations/standards-policies/. Verified on 21 November 2026.
  45. S45The National, "Almost 300 arrested in joint UAE, US, Chinese crackdown on financial crime", 29 April 2026. https://www.thenationalnews.com/news/uae/2026/04/29/almost-300-arrested-in-joint-uae-us-chinese-crackdown-on-financial-crime/. Verified on 21 November 2026.
  46. S46The National, "UAE leads 39 billion USD global digital fraud crackdown with more than 900 arrests", 22 October 2026. https://thenationalnews.com/news/uae/2026/10/22/uae-leads-39-billion-global-digital-fraud-crackdown-with-more-than-900-arrests. Verified on 21 November 2026.
  47. S47Gulf News, "Dubai Police warn of rise in fake calls posing as officials and banks", 11 April 2026. https://gulfnews.com/uae/crime/dubai-police-warn-of-rise-in-fake-calls-posing-as-officials-and-banks-1.500503458. Verified on 21 November 2026.
  48. S48Khaleej Times, Dubai Police warning on fake consumer-protection links, 7 July 2026. https://www.khaleejtimes.com/uae/dubai-police-fake-consumer-protection-links-banking-scam-warning. Verified on 21 November 2026.
  49. S49Emarat Al Youm, Dubai Police warning on callers posing as crisis-management staff (Arabic), 2 March 2026. https://www.emaratalyoum.com/local-section/accidents/2026-03-02-1.2020925. Verified on 21 November 2026.
  50. S50Khaleej Times, Abu Dhabi Police warning on fake social-media accounts, 25 April 2026. https://www.khaleejtimes.com/uae/fake-social-media-accounts-visa-concert-ticket-property-scam. Verified on 21 November 2026.
  51. S51Sharjah24, Sharjah Police arrests in a remote-access impersonation scam, 5 July 2026. https://sharjah24.ae/en/Articles/2026/07/05/mm07. Verified on 21 November 2026.
  52. S52Khaleej Times, "Dubai Police arrest gang over shopping website scam", 23 October 2026. https://www.khaleejtimes.com/crime/dubai-police-arrest-gang-shopping-website-scam-steal-bank-details. Verified on 21 November 2026.
  53. S53Khaleej Times, DFSA warning on fresh online scams and fake firms, 9 March 2026 (DFSA alert of 5 March). https://www.khaleejtimes.com/uae/dubai-regulator-warns-fresh-online-scams-fake-firms-dfsa-permit. Verified on 21 November 2026.
  54. S54Sharjah24, UAE Cabinet approves the UAE Cybersecurity Council, 29 November 2020. https://sharjah24.ae/en/Articles/2020/11/29/VP-approves-UAE-Environment-Policy-UAE-Cybersecurity-Council-and-UAE-National-Media-Team. Verified on 21 November 2026.
  55. S55Zawya (WAM), "World Economic Forum recognises UAE PASS as global digital government model" (undated page). https://www.zawya.com/en/business/world-economic-forum-recognises-uae-pass-as-global-digital-government-model-402881. Verified on 21 November 2026.
  56. S56Federal Decree-Law No. (34) of 2021 on Countering Rumors and Cybercrimes, English text hosted by ADGM (issued 20 September 2021; in force 2 January 2022). https://assets.adgm.com/download/assets/Federal%2BDecreeLaw%2BNo%2B34%2Bof%2B2021%2BOn%2BCountering%2BRumors%2Band%2BCybercrimes.pdf/7b3c845c864f11ef8ccdca0b2c1f6c13. Verified on 21 November 2026.
  57. S57Gulf News, "UAE overhauls bank risk rules: 4-hour reporting, cyber tests and tougher penalties", updated 15 September 2026. https://gulfnews.com/business/banking/uae-overhauls-bank-risk-rules-4-hour-reporting-cyber-tests-and-tougher-penalties-1.500675080. Verified on 21 November 2026.
  58. S58Check Point Research, "Interplay between Iranian targeting of IP cameras and physical warfare in the Middle East", 4 March 2026. https://research.checkpoint.com/2026/interplay-between-iranian-targeting-of-ip-cameras-and-physical-warfare-in-the-middle-east/. Verified on 21 November 2026.
  59. S59NIST NVD, CVE-2017-7921 (Hikvision cameras, improper authentication; CVSS 3.1 9.8; added to CISA KEV 5 March 2026). https://nvd.nist.gov/vuln/detail/CVE-2017-7921. Verified on 21 November 2026.
  60. S60NIST NVD, CVE-2021-33044 (Dahua devices, authentication bypass; CVSS 3.1 9.8; added to CISA KEV 21 August 2024). https://nvd.nist.gov/vuln/detail/CVE-2021-33044. Verified on 21 November 2026.
  61. S61Netcraft, "Middle East crisis: opportunistic fraud", 10 March 2026. https://netcraft.com/blog/middle-east-crisis-opportunistic-fraud. Verified on 21 November 2026.
  62. S62Khaleej Times, report on a cross-emirate fake traffic-fine SMS network, 11 April 2026. https://www.khaleejtimes.com/uae/crime/dh4-traffic-fine-cross-emirate-fraud-network-busted-over-fake-sms-scam. Verified on 21 November 2026.
  63. S63Gulf News, "UAE warns against phone scams, fake websites impersonating ICP logo", 30 April 2026. https://gulfnews.com/uae/government/uae-warns-against-phone-scams-fake-websites-impersonating-icp-logo-1.500524560. Verified on 21 November 2026.
  64. S64Palo Alto Networks Unit 42, threat brief on Iranian cyber activity in 2026, 17 April 2026. https://unit42.paloaltonetworks.com/iranian-cyberattacks-2026/. Verified on 21 November 2026.
  65. S65The National, report on a finance conference's attendee-document exposure, 18 February 2026. https://www.thenationalnews.com/ (article URL withheld). Verified on 21 November 2026.
  66. S66DeXpose, report of a claim against a UAE customs authority, 22 August 2026. https://www.dexpose.io/ (article URL withheld). Verified on 21 November 2026.
  67. S67Gulf News, "A hacker accessed sensitive UAE-linked systems then demanded $5m", 15 September 2026. https://gulfnews.com/living-in-uae/safety-security/a-hacker-accessed-sensitive-uae-linked-systems-then-demanded-5m-1.500675569. Verified on 21 November 2026.
  68. S68CISA (ICS-CERT), advisory ICSA-17-124-01, Hikvision IP cameras (CVE-2017-7921), 4 May 2017. https://www.cisa.gov/news-events/ics-advisories/icsa-17-124-01. Verified on 21 November 2026.
  69. S69Dahua, security advisory DHCC-SA-202106-001, identity authentication bypass in some Dahua products (CVE-2021-33044), 1 September 2021, updated 15 November 2021. https://www.dahuasecurity.com/about-dahua/trust-center/dahua-psirt/dhcc-sa-202106-001:security-advisory---identity-authentication-bypass-vulnerability-found-in-some-dahua-products. Verified on 21 November 2026.

Appendix D. Glossary

  • Blackhole: Brandefense's cybercrime data source covering posts, infected devices, credentials and card material.
  • Ransompedia: Brandefense's ransomware database; listings record criminal claims.
  • Atlas: Brandefense's external exposure scoring; scores run from 0 (nothing observed) to 100.
  • Infected device: a device with information-stealing malware that Brandefense associates with the organisation's domain; "employee" is Brandefense's classification, not verified employment.
  • Credential-market listing: a credential tied to the domain offered on a monitored market at the time of the check.
  • Combolist: a list of login and password pairs assembled from various sources; age and validity vary.
  • Stealer log: data captured by information-stealing malware from a device.
  • Checker bot: a bot that tests stolen cards against payment gateways and prints the result.
  • Wiper: malware that destroys data rather than encrypting it for ransom.
  • Mule account: a bank or wallet account lent or sold to move proceeds of fraud.
  • KYC (know your customer): identity checks at account opening; "KYC services" sell accounts that have already passed them.
  • Availability-check link: a link to a public service that tests whether a site answers from a few locations; it captures a moment, not an outage.
  • Hack-and-leak: an operation that publishes stolen material to cause damage or pressure, sometimes with destructive claims.
  • Post card: a redacted reproduction of one dark-web post, with venue, date, alias, language and what it does and does not establish.
  • Relay: a third-party channel or bot that reposts another actor's claim; a relay is weaker evidence than the actor's own post.
  • DMARC / SPF / DKIM: email-authentication standards; DMARC tells receivers what to do with mail that fails.
  • DNSSEC: signatures that let resolvers verify DNS answers.
  • TLP:CLEAR: may be shared without restriction; other legal duties still apply.
  • Lookalike domain: a newly observed domain that resembles an organisation's own; a candidate for phishing, not a confirmed phishing site.
  • Card dumps: copied magnetic-stripe data used to clone cards for card-present cash-out.
  • Accepted listing: a Ransompedia leak-site listing kept after rejected and duplicate entries are removed.
  • OT (operational technology): systems that run physical processes, such as power, water and industrial control.
  • HSTS: a web header that tells browsers to use HTTPS only.
  • End-of-life: software no longer receiving security updates from its vendor.

About this report

Prepared by Odin by Brandefense. Version 1.0 was completed on 21 November 2026. Research cutoff: 20 November 2026 for posts, ransomware listings and public reporting; exposure data were read on 21 November 2026. The report prioritises Brandefense's own data, keeps criminal claims separate from independently established incidents and does not claim a complete census of cybercrime affecting the UAE. The authors take no position on the policies of any government; attributions are reported as their sources state them. Recommendations describe what organisations could do; they do not state that any organisation has or has not done them. An Arabic edition is available; where the editions differ, the English edition prevails.

© 2026 Brandefense. All rights reserved.