Cyber Situation Report Switzerland, Week 44/2026
Voluntary reports to the NCSC per week, last 52 weeks
Report categories in the reporting week
Ransomware cases in Switzerland most recently listed on leak sites
Sources: NCSC reporting statistics and ransomware.live, data as of this edition. Only publicly reported or visible activity is recorded. The names of the organisations listed were published by the ransomware groups themselves. Initcon does not add names and does not assess individual cases. “Entries according to ransomware.live” counts the leak-site entries of the 365 days up to the end of the reporting week that ransomware.live attributes to Switzerland; entries whose description places the organisation in another country are not counted. Sectors follow the ransomware.live classification.
The situation in three sentences
Voluntary reports submitted to the NCSC stand at 1,255, slightly above the previous week, driven by continued high numbers in phishing and fraud attempts. In the reporting week, Holcim, a listed major construction materials company, appeared on ransomware leak sites, whilst over the past 90 days smaller Swiss firms have predominantly featured on leak sites. Attack patterns remain stable; both large and small organisations are affected.
Key figures for the week
- Reporting period: 26 October 2026 to 1 November 2026
- Voluntary reports submitted to the NCSC: 1,255, compared to 1,200 in the previous week (plus 55)
- Phishing: 517 reports, the largest single category
- Fraud attempts: 323 reports
- Spam: 196 reports
- Other categories: 219 reports
- Ransomware cases listed on leak sites in Switzerland over the past 90 days: 36, of which one in the reporting week (Holcim)
Assessment for the board of directors and executive management
The picture from the reporting statistics shows little structural change. Phishing and fraud attempts together account for 840 of the 1,255 reports, making up by far the largest share of incidents. Attacks primarily target the person at the screen. For oversight, this means the relevant line of defence lies in processes, authorisations and payment approvals, areas that the board of directors can control through directives and reviews.
Ransomware cases show a different pattern. In the reporting week, Holcim, an internationally operating, listed company, appeared on a leak site. Over the past 90 days, however, smaller and medium-sized Swiss companies from industry, trade, healthcare and consulting have dominated. A single attacker group, safepay, is behind eight of the 36 cases and targets primarily smaller organisations, including public institutions. The breadth of affected sectors shows that companies cannot rely on remaining inconspicuous.
For the board of directors and executive management, both aspects touch on overall management and overall supervision under Art. 716a OR. The board must be able to rely on the executive management having worked through how a successful attack would unfold: who decides how long operations can continue without IT, and what happens if stolen data are published. Holcim confirmed the data breach. In such cases, a simple restoration from backup does not solve the problem.
Three questions for executive management
- Which payment and approval processes are designed so that a single deceived person cannot trigger a material payment or data release alone, and when was this last verified against a real phishing incident?
- For how long can our core business continue without central IT systems, and is there a communication and decision plan in place for the publication of stolen data that goes beyond technical restoration?
- Which of our suppliers and service providers experienced a known security incident in recent months, and which dependencies on these partners would affect us if they were to fail?
Data are based on the public statistics of voluntary reports submitted to the National Cyber Security Centre (NCSC) and ransomware cases listed on leak sites according to ransomware.live. The figures reflect only publicly reported or visible activity.
Corrected on 9 November 2026: figures following revision of the NCSC statistics, formulations regarding leak site entries, terminology