Dark Tide — Incident Brief
National Cybersecurity Incident Response TeamExercise material   /   September 2026
Case reference   DT–2026 / 01Priority: critical

DARK TIDE

INCIDENT BRIEFInitial notification
14 September 2026
Hydronex Systems   /   Water-sector infrastructureVersion 1.0
River channels traced across a dark survey sheet010203
WATER / AUTOMATION / CONTROL SYSTEMS
DT–2026
SECTOR REFERENCE SHEET
01 / SituationInitial report

Encryption reported across the Hydronex estate

At 05:42 on Monday morning, Hydronex Systems requests urgent assistance following a major cyber incident affecting its Windows servers and workstations.

The organization declared the incident at approximately 04:37. Files have been encrypted, several systems are unavailable and backup services are no longer responding. Administrators report unusual privileged authentication, abnormal SMB traffic and a ransom note on multiple machines.

Hydronex supplies automation, monitoring and engineering technology to the water sector. Its technology and services are used by utilities serving approximately 80% of the country's population. Several engineering resources are unreachable; the extent of customer exposure is unknown.

Current assessment. There is no confirmed evidence of physical disruption to water treatment or distribution.

Your team has been assigned the available endpoint, network, identity and engineering evidence. Hydronex cannot yet establish the entry point, the duration of the intrusion or whether information left its network.

Questions for the response team

  1. When did the intrusion begin, and how was access obtained?
  2. Which identities and systems were involved?
  3. What information was collected or transferred?
  4. Did the activity reach operational technology, and what impact can be demonstrated?
Open case evidence →

Begin with the available challenges. Further lines of investigation open as you progress.

02 / Reference

Working instructions

Evidence handling and submissions

Analyze working copies and retain the original packages. Record the source of each finding. Submit answers as DARKTIDE{answer}, using the exact format requested in each challenge. Not every unusual event belongs to this incident.

Time references

The briefing uses UTC+02:00. Evidence retains its original timestamp offset; some exports also include a separate UTC field. Distinguish event time from collection or ingestion time. Follow the timezone requested in the question.

Tools and permitted assistance

Bring Wireshark, a SQLite viewer, an email parser and your preferred scripting tools. AI assistance is permitted, but conclusions must be verified against the supplied artifacts. Obtain organizer approval before uploading evidence to an external service. All investigation targets are fictional; work offline with the provided files.

Reporting operational impact

Separate observed access, attempted commands, device responses and measured process effects. A gap in telemetry is a limitation to report. It does not establish either damage or the absence of damage.