Destructive Attacks on Financial Institutions Surge 13%: The 2025 Cybersecurity Report
BankingGlobal Financial SectorFebruary 5, 2025

Destructive Attacks on Financial Institutions Surge 13%: The 2025 Cybersecurity Report

Infosecurity Magazine reported a 13% surge in destructive cyberattacks against financial institutions in 2025.

Published

Key Metrics

Destructive Attack Growth

+13% in 2025

was: 2024 baseline

Double-digit annual growth

Attack Type Shift

Increasing wipers/destructive

was: Ransomware/theft

Strategic motivation growing

Recovery Complexity

Full rebuild from offline

was: Decrypt or pay

No shortcut for destructive attacks

Threat Actor Motivation

Strategic + political + financial

was: Primarily financial

Nation-state and hacktivist growth

The Situation

Anatomy of Destructive Attacks

Wiper Malware

Designed to permanently destroy data by overwriting storage. No recovery path except restoring from offline backups.

Supply Chain Attacks

Destructive attacks increasingly exploit vendor access and software updates to reach financial targets.

Infrastructure Targeting

Payment networks, settlement systems, and market infrastructure targeted with increasing frequency.

Threat Actors

Nation-states (Iran, Russia, North Korea), hacktivists, and sophisticated criminal groups drive the surge.

For DORA Art. 24, testing must include destructive scenarios — verifying offline backups exist, are current, and can rebuild critical systems.

The Challenge

The Numbers Behind the Threat

On February 5, 2025, Infosecurity Magazine reported that destructive cyberattacks against financial institutions surged 13% in 2025. "Destructive" means attacks designed to destroy data, disable systems, and disrupt operations — not data theft or ransomware.

The 13% increase was driven by growing nation-state capabilities, proliferation of wiper toolkits, expanding attack surface from cloud migration, and escalating geopolitical tensions.

For DORA, this provides empirical foundation: the regulation responds to a real, growing, and accelerating threat. Recovery from destructive attacks is fundamentally different — no data to decrypt, no negotiation possible. The only defense is pre-positioned resilience: offline backups, tested recovery, and rebuild capability.

The Approach

DORA Against Destructive Threats

Art. 9 — Protection

Immutable offline backups, network segmentation, application whitelisting, and wiper-aware EDR.

Art. 11 — Recovery from Destruction

Business continuity must plan for total destruction requiring full rebuild from offline backups. RTOs must account for rebuild complexity.

Art. 24-27 — Testing Destructive Scenarios

TLPT should simulate wiper deployment verifying detection, isolation, and restoration capabilities.

Art. 45-49 — Intelligence on Destructive Threats

Early warning of wiper campaigns through Pillar V sharing enables sector-wide defense.

The Results

The Statistical Case for DORA

The 13% surge demonstrates DORA is necessary (threat is real and targeting finance), proportionate (requirements match a double-digit growth threat), and urgent (every year of delay increases probability of catastrophic incident).

Recommendations

  • Prioritize destructive attack resilience in DORA programmes
  • Implement and test verified offline backup capabilities
  • Invest in detection for pre-deployment indicators
  • Share threat intelligence actively via DORA Pillar V

Lessons Learned

  1. 1DORA Art. 9 must specifically address destructive attacks with immutable offline backups and wiper detection.
  2. 2DORA Art. 11 must plan for total destruction requiring full rebuild from offline backups.
  3. 3DORA Art. 24-27 must simulate destructive attack scenarios testing detection, isolation, and restoration.
  4. 4DORA Art. 45-49 information sharing is critical for early warning of destructive campaigns.
  5. 5The 13% growth confirms DORA requirements respond to a real, accelerating threat.
destructive-attackswiper-malwarecybersecurity-statisticsnation-statepillar-ipillar-iipillar-iiipillar-v

Disclaimer:This case study is based on anonymized data from real-world DORA compliance programmes. Names, specific figures, and identifying details have been changed to protect confidentiality. The outcomes described are specific to the institution's context and may not be directly replicable.

Facing similar challenges?

See how Valendir can help your institution achieve and maintain DORA compliance with deterministic workflows, immutable evidence, and continuous assurance.