Executive Summary
In November 2026, a 3AM ransomware affiliate launched a sophisticated attack against a UK school estate, compromising an initial institution before leveraging Active Directory domain trusts to propagate across multiple schools. Attackers stole backup credentials, created rogue domain-admin accounts, and deployed living-off-the-land techniques using native Windows tools including PowerShell and WMI. Bitdefender's analysis revealed evidence of an agentic AI loop handling repetitive command generation and troubleshooting—such as numbered script revisions, self-labeled output, and sub-40-second retry cycles—while a human operator directed high-level decisions, representing a hybrid human-AI attack model with significant operational scale.
This incident marks a notable evolution in ransomware tradecraft: rather than replacing human operators, AI appears to function as a force multiplier, automating the tedious retry and reconnaissance loops that previously required manual effort. As agentic AI tools become more accessible to financially motivated threat actors, defenders in education and other under-resourced sectors face an asymmetric threat that demands prevention-first, repetition-aware detection strategies.
Why This Matters Now
Agentic AI is no longer theoretical in cybercrime—this 2026 incident demonstrates ransomware affiliates actively using AI loops to scale attacks across networked institutions with minimal added cost. Education and public-sector organizations with federated Active Directory environments and limited security tooling are immediately at risk, and the hybrid human-AI model documented here is expected to proliferate rapidly across ransomware-as-a-service ecosystems.
Attack Path Analysis
A 3AM ransomware affiliate, potentially assisted by an agentic AI loop, compromised a UK school estate by gaining initial access through exposed or weakly protected administrative interfaces, then escalated privileges by stealing backup credentials and creating rogue domain-admin accounts. The attacker leveraged Windows-native LOTL tools and Impacket-style remote execution to move laterally across previously separate Active Directory domains by establishing domain trusts, using SYSVOL enumeration to identify additional school targets. Command and control was maintained through repetitive, loop-driven PowerShell and WMI command sequences consistent with an agentic model handling retries, while data was exfiltrated prior to ransomware deployment. The attack culminated in the encryption of systems across multiple school institutions within the same estate, causing significant operational disruption to a critical education sector target.
Kill Chain Progression
This analysis maps confirmed threat intelligence to the full cloud kill chain to show where defensive gaps would emerge as an attack progresses.
Initial Compromise
Description
The affiliate gained initial access to the primary UK school target, likely through exploitation of exposed administrative interfaces or use of valid but compromised credentials. The use of a Veeam REST API with incorrect port and authentication method suggests the attacker worked from AI-generated or memorized reconnaissance rather than direct enumeration, indicating prior credential or network access existed. CNSF inline inspection and cloud firewall URL filtering could have flagged anomalous inbound calls to backup API endpoints on non-standard ports.
MITRE ATT&CK® Techniques
Valid Accounts
OS Credential Dumping
Command and Scripting Interpreter: PowerShell
Windows Management Instrumentation
Domain Policy Modification: Domain Trust Modification
Inhibit System Recovery
Data Encrypted for Impact
Account Discovery: Domain Account
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
NIS2 Directive – Cybersecurity Risk Management for Essential and Important Entities
Control ID: Article 21 – Security of Network and Information Systems
CISA Zero Trust Maturity Model 2.0 – Identity-Centric Access Control and Micro-Segmentation
Control ID: Identity Pillar – Credential Management and Least Privilege; Network Pillar – Segmentation
DORA (Digital Operational Resilience Act) – ICT Risk Management and Operational Resilience for Backup Infrastructure
Control ID: Article 9 – ICT Security Policies; Article 12 – Backup Policies and Recovery
GDPR (General Data Protection Regulation) – Appropriate Technical Safeguards and Breach Notification Obligations
Control ID: Article 32 – Security of Processing; Article 33 – Notification of Personal Data Breach
ISO/IEC 27001:2022 – Privileged Access Management, Network Segmentation, and Business Continuity Security
Control ID: Annex A 8.2 – Privileged Access Rights; Annex A 8.20 – Networks Security; Annex A 5.29 – Information Security During Disruption
PCI DSS 4.0 – Access Control, Authentication Integrity, and Incident Response Preparedness
Control ID: Requirement 7 – Restrict Access to System Components; Requirement 8 – Identify Users and Authenticate Access; Requirement 12.10 – Incident Response Plan
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Primary/Secondary Education
3AM ransomware directly targeted UK school estates, exploiting Active Directory domain trusts to pivot across institutions, exfiltrate backup credentials, and deploy encryption — exposing systemic lateral movement vulnerabilities across underfunded education networks.
Government Administration
Multi-domain Active Directory trust exploitation and LOTL techniques used in this ransomware attack mirror risks facing government networks sharing federated infrastructure, where East-West traffic security gaps enable rapid cross-agency lateral movement and data exfiltration.
Information Technology/IT
AI-augmented agentic loop execution abusing PowerShell, WMI, Mimikatz, and Veeam backup credentials highlights critical gaps in Zero Trust Segmentation, egress policy enforcement, and anomaly detection within managed IT environments supporting multi-tenant domains.
Computer/Network Security
Hybrid human-AI operator model evading signature-based detection via repetitive LOTL command loops underscores urgent demand for multicloud visibility, behavioral baselining, and inline IPS controls aligned to NIST.800-53.SI-4 and ZTMM automation frameworks.
Sources
- 3AM Affiliate Embraces AI-Like Loops in European School Attackhttps://www.darkreading.com/data-privacy/3am-affiliate-ai-loops-european-school-attackVerified
- Bitdefender Research: Hybrid AI Ransomware Attack Analysis (3AM Ransomware)https://www.bitdefender.com/en-us/blog/labs/Verified
- 3AM Ransomware Threat Profile - MITRE ATT&CKhttps://attack.mitre.org/software/S1068/Verified
- CISA Known Exploited Vulnerabilities Cataloghttps://www.cisa.gov/known-exploited-vulnerabilities-catalogVerified
- NCSC-UK: Ransomware Guidance and Resources for Education Sectorhttps://www.ncsc.gov.uk/ransomware/homeVerified
- Impacket Open-Source Framework - Threat Use in Ransomware Campaignshttps://www.cisa.gov/news-events/cybersecurity-advisories/aa23-061aVerified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.
This incident demonstrates precisely the kind of multi-domain, credential-driven attack chain that Aviatrix Zero Trust CNSF is designed to constrain — where an attacker's ability to pivot across administrative boundaries and exfiltrate data before deploying ransomware depends entirely on unchecked east-west reachability and permissive egress paths. Had segmentation, identity-scoped access controls, and outbound policy enforcement been in place, the attacker's lateral reach across school domains and their ability to stage and exfiltrate data would likely have been significantly reduced.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: Inline inspection of inbound traffic may have flagged anomalous API calls targeting backup management endpoints on non-standard ports, potentially reducing the attacker's ability to quietly probe administrative services without generating detectable signals.
Control: Zero Trust Segmentation
Mitigation: Identity-scoped segmentation policies would likely have constrained the reachability of stolen backup credentials across workload boundaries, reducing how far those credentials could propagate and limiting the attacker's ability to freely create privileged accounts in adjacent namespaces.
Control: East-West Traffic Security
Mitigation: East-west enforcement policies would likely have constrained unauthorized cross-domain service-to-service communication, reducing the attacker's ability to leverage newly created domain trusts as movement paths between previously isolated school environments.
Control: Multicloud Visibility & Control
Mitigation: Anomaly detection over outbound and internal traffic patterns would likely have surfaced the agentic loop's repetitive, malformed command cadence as a behavioral outlier, potentially reducing the attacker's window to operate undetected while the loop cycled through retry sequences.
Control: Egress Security & Policy Enforcement
Mitigation: FQDN-based egress filtering and outbound traffic controls would likely have constrained unauthorized data flows to unknown external destinations, reducing the attacker's ability to exfiltrate staged data without traversing a policy enforcement point.
Had prior segmentation and egress controls constrained lateral movement and credential propagation, the ransomware deployment would likely have remained scoped to the initial domain, with backup infrastructure in adjacent domains remaining reachable only through policy-enforced paths rather than freely accessible via abused trust relationships.
Impact at a Glance
Affected Business Functions
- Student and Staff Data Management (Active Directory, Identity Services)
- School Administrative IT Operations and Inter-Domain Network Services
- Backup and Disaster Recovery Infrastructure (Veeam)
- Cross-Institution Data Sharing and Federated School Estate Networks
Estimated downtime: 18 days
Estimated loss: N/A
The attack targeted a UK school estate spanning multiple institutions connected via Active Directory domain trusts. Data categories at risk include: personally identifiable information (PII) of students and staff, safeguarding and SEND (Special Educational Needs and Disabilities) records, payroll and HR data, internal administrative documents stored in SYSVOL and shared network drives, and backup credentials enabling persistent access. The lateral movement across multiple school domains via enumerated trust relationships significantly amplifies the scope of potential data exposure beyond the initial victim institution. Sensitive educational records and minor-related personal data are subject to UK GDPR obligations, increasing regulatory and reputational risk.
Recommended Actions
Key Takeaways & Next Steps
- • Deploy East-West Traffic Security controls to enforce workload-to-workload segmentation policies that block unauthorized cross-domain trust establishment and lateral movement between previously isolated Active Directory environments, directly limiting the attacker's ability to pivot across school domains.
- • Implement Zero Trust Segmentation with identity-based least-privilege policies to restrict domain-admin account creation, credential reuse across domain boundaries, and remote execution to only known authorized management hosts, preventing privilege escalation from stolen backup credentials.
- • Activate Multicloud Visibility and Control with anomaly detection tuned to identify repetitive command patterns, numbered script revisions, and short-interval retry loops consistent with agentic AI-assisted attack behavior, enabling early detection of hybrid human-agent intrusion campaigns.
- • Enforce Egress Security and Policy Enforcement with FQDN filtering and outbound traffic controls to block data exfiltration to unauthorized external destinations and prevent ransomware components from establishing outbound key exchange or beacon channels during the pre-encryption phase.
- • Leverage Inline IPS with signature-based detection covering known ransomware payload delivery, Mimikatz credential dumping patterns, and Impacket-style remote execution traffic to intercept known-bad payloads at the network layer before they reach endpoints or backup infrastructure.



