3AM ransomware affiliate using AI loop against UK schools
3AM ransomware affiliate used AI loop against UK schools showing model-style command errors including Bash escape sequences in Windows commands and malformed for /f syntax passing K" to comsvcs. Numbered…
What happened
3AM ransomware affiliate used AI loop against UK schools showing model-style command errors including Bash escape sequences in Windows commands and malformed for /f syntax passing K" to comsvcs. Numbered retry scripts (av_remove2, av_remove3) indicate automated iteration. Probe files da_proof.txt and psexec-ok suggest autonomous validation. Backdoor admins library and svc_bkpmon created. Staging registry path HKLM\SOFTWARE\FIN001. Attack demonstrates AI-driven operations with observable execution errors and iteration patterns.
How it happened
Read the flow as text & sources
A catalog reconstruction of the supplied source account. Unknown steps remain explicit; an edge describes the reported relationship between steps.
- 01 · Initial access to UK schools
Initial access vector not disclosed in source
Source for step 1 - 02 · AI loop generates attack commands
Model generates commands with observable errors including Bash escapes in Windows commands and broken for /f syntax
Hunt: A script host or shell runs encoded content, a remote URL, or inline script syntax, then downloads or launches a payload.
Encoded commands and remote administration can be legitimate. This does not cover every script host, in-process execution, or non-Windows branch.
Source for step 2 - 03 · Automated retry with numbered scripts
Numbered scripts av_remove2, av_remove3 show iteration; probe files da_proof.txt, psexec-ok validate steps
Hunt: A script host or shell runs encoded content, a remote URL, or inline script syntax, then downloads or launches a payload.
Encoded commands and remote administration can be legitimate. This does not cover every script host, in-process execution, or non-Windows branch.
Source for step 3 - 04 · Backdoor accounts and registry staging
Backdoor admins library and svc_bkpmon created; staging in HKLM\SOFTWARE\FIN001
Hunt: A task, Run key, cron entry, shell profile, or startup file is changed and later launches the same unexpected program.
Windows and Unix persistence require different collectors. A configuration change without a subsequent launch is not proof that persistence ran.
Source for step 4 - 05 · 3AM ransomware deployed
3AM ransomware payload deployed after preparation
Hunt: A process rapidly enumerates or modifies sensitive files and is followed by encryption, export or a ransom-related artifact.
A file-write burst is not proof of ransomware; in-process interpreters may not spawn a separate executable.
Source for step 5
Why it matters
Reported impact: 3AM ransomware payload deployed after preparation; reported targets include UK schools; applicability to your setup has not been assessed, so verify affected versions, permissions, and configuration in the original report.
What you can do
Protection & prevention
Detect model-style command syntax errors; monitor for numbered retry scripts; alert on probe files in unusual locations; review backdoor account creation; monitor registry key HKLM\SOFTWARE\FIN001; detect PsExec lateral movement; hunt for comsvcs.dll credential dumping
Catalog defensive guidance based on the reported behavior. Confirm scope and current mitigations in the original source.
Detection queries
Draft query starters grouped by the attack stages where they apply.
Start with the logs you collect. Each hunt identifies its required visibility, field mapping and limits. Queries are catalog-authored drafts using reusable behavior profiles; test with known activity and your normal baseline before alerting.
02AI loop generates attack commandsSuspicious Windows script executionNative logs · Draft
Model generates commands with observable errors including Bash escapes in Windows commands and broken for /f syntax
What to look for
A script host or shell runs encoded content, a remote URL, or inline script syntax, then downloads or launches a payload.
Apply the process hunt to the generated Windows commands and their parent process; syntax errors alone are not malicious.
Visibility: Defender-side logs where collected
Required logs
- Windows process creation: Sysmon Event 1 or Defender DeviceProcessEvents
- PowerShell script-block logging when enabled
- Download / network and installer events
Coverage limit. Encoded commands and remote administration can be legitimate. This does not cover every script host, in-process execution, or non-Windows branch.
Windows process candidates. Sigma uses normalized process_creation fields; KQL requires Defender for Endpoint; SPL requires the Sysmon XML sourcetype. Tune collectors, fields and baselines before use.
Sigma
title: Hunt - Suspicious Windows script execution
id: 2bb88802-9f03-4d99-a192-fe44c9484e8b
status: experimental
description: A script host or shell runs encoded content, a remote URL, or
inline script syntax, then downloads or launches a payload.
author: MagicSword OpenAttacks catalog
date: 2026-10-23
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: process_creation
product: windows
detection:
selection:
Image|endswith:
- \powershell.exe
- \pwsh.exe
- \mshta.exe
- \wscript.exe
- \cscript.exe
CommandLine|contains:
- -enc
- http
- FromBase64String
- "javascript:"
- "vbscript:"
condition: selection
KQL
// Draft hunt; requires Defender for Endpoint process telemetry for this OS.
DeviceProcessEvents
| where Timestamp > ago(7d)
| where FileName in~ ("powershell.exe", "pwsh.exe", "mshta.exe", "wscript.exe", "cscript.exe")
| where ProcessCommandLine contains "-enc" or ProcessCommandLine contains "http" or ProcessCommandLine contains "FromBase64String" or ProcessCommandLine contains "javascript:" or ProcessCommandLine contains "vbscript:"
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessFileName, InitiatingProcessCommandLine, SHA1
| order by Timestamp descSPL
sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1
Image IN ("*\\powershell.exe", "*\\pwsh.exe", "*\\mshta.exe", "*\\wscript.exe", "*\\cscript.exe")
CommandLine IN ("*-enc*", "*http*", "*FromBase64String*", "*javascript:*", "*vbscript:*")
| table _time host User Image CommandLine ParentImage ParentCommandLine
| sort - _timeInvestigation steps
- Follow the parent and child process tree and recover the script or URL from logs without executing it.
- Correlate the payload's signer/hash, persistence, and network activity; baseline approved automation.
03Automated retry with numbered scriptsSuspicious Windows script executionNative logs · Draft
Numbered scripts av_remove2, av_remove3 show iteration; probe files da_proof.txt, psexec-ok validate steps
What to look for
A script host or shell runs encoded content, a remote URL, or inline script syntax, then downloads or launches a payload.
Visibility: Defender-side logs where collected
Required logs
- Windows process creation: Sysmon Event 1 or Defender DeviceProcessEvents
- PowerShell script-block logging when enabled
- Download / network and installer events
Coverage limit. Encoded commands and remote administration can be legitimate. This does not cover every script host, in-process execution, or non-Windows branch.
Windows process candidates. Sigma uses normalized process_creation fields; KQL requires Defender for Endpoint; SPL requires the Sysmon XML sourcetype. Tune collectors, fields and baselines before use.
Sigma
title: Hunt - Suspicious Windows script execution
id: 2bb88802-9f03-4d99-a192-fe44c9484e8b
status: experimental
description: A script host or shell runs encoded content, a remote URL, or
inline script syntax, then downloads or launches a payload.
author: MagicSword OpenAttacks catalog
date: 2026-10-23
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: process_creation
product: windows
detection:
selection:
Image|endswith:
- \powershell.exe
- \pwsh.exe
- \mshta.exe
- \wscript.exe
- \cscript.exe
CommandLine|contains:
- -enc
- http
- FromBase64String
- "javascript:"
- "vbscript:"
condition: selection
KQL
// Draft hunt; requires Defender for Endpoint process telemetry for this OS.
DeviceProcessEvents
| where Timestamp > ago(7d)
| where FileName in~ ("powershell.exe", "pwsh.exe", "mshta.exe", "wscript.exe", "cscript.exe")
| where ProcessCommandLine contains "-enc" or ProcessCommandLine contains "http" or ProcessCommandLine contains "FromBase64String" or ProcessCommandLine contains "javascript:" or ProcessCommandLine contains "vbscript:"
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessFileName, InitiatingProcessCommandLine, SHA1
| order by Timestamp descSPL
sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1
Image IN ("*\\powershell.exe", "*\\pwsh.exe", "*\\mshta.exe", "*\\wscript.exe", "*\\cscript.exe")
CommandLine IN ("*-enc*", "*http*", "*FromBase64String*", "*javascript:*", "*vbscript:*")
| table _time host User Image CommandLine ParentImage ParentCommandLine
| sort - _timeInvestigation steps
- Follow the parent and child process tree and recover the script or URL from logs without executing it.
- Correlate the payload's signer/hash, persistence, and network activity; baseline approved automation.
04Backdoor accounts and registry stagingNew persistence → recurring executionCustom schema · Draft
Backdoor admins library and svc_bkpmon created; staging in HKLM\SOFTWARE\FIN001
What to look for
A task, Run key, cron entry, shell profile, or startup file is changed and later launches the same unexpected program.
Visibility: Defender-side logs where collected
Required logs
- Platform-specific registry, scheduled-task, cron and startup-file changes
- Process creation and file provenance
- User / administrative change records
Coverage limit. Windows and Unix persistence require different collectors. A configuration change without a subsequent launch is not proof that persistence ran.
Custom-schema candidates, not out-of-box detectors. Map your application / cloud / platform logs to EventType, Actor, Asset, Action, Target and CorrelationId. KQL uses a custom OpenAttacksAudit_CL table; SPL uses openattacks:audit. EventType values are proposed normalization names, not native vendor event names. Correlation and environment-specific alert logic remain to be built.
Sigma
title: Hunt - New persistence → recurring execution
id: 6154ff56-2978-45fa-aecd-86d91557f32e
status: experimental
description: A task, Run key, cron entry, shell profile, or startup file is
changed and later launches the same unexpected program.
author: MagicSword OpenAttacks catalog
date: 2026-10-23
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: application
product: openattacks_audit
definition: Custom normalized audit schema; map EventType, Actor, Asset, Action,
Target and CorrelationId from the required source logs first.
detection:
selection:
EventType:
- persistence.create
- persistence.modify
condition: selection
KQL
// SCHEMA TEMPLATE: create/map this custom table before use; not a built-in Sentinel table.
// OpenAttacksAudit_CL: TimeGenerated(datetime), EventType/Actor/Asset/Action/Target/CorrelationId(string).
// Selects candidates only. Apply the stage hypothesis and correlation steps before alerting.
OpenAttacksAudit_CL
| where TimeGenerated > ago(7d)
| where EventType in ("persistence.create", "persistence.modify")
| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId
| order by TimeGenerated descSPL
sourcetype="openattacks:audit"
EventType IN ("persistence.create", "persistence.modify")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _timeInvestigation steps
- Diff the persistence artifact and identify the creating process / principal.
- Correlate the subsequent launch and network behavior; baseline deployment and management agents.
053AM ransomware deployedCollection / encryption behaviorCustom schema · Draft
3AM ransomware payload deployed after preparation
What to look for
A process rapidly enumerates or modifies sensitive files and is followed by encryption, export or a ransom-related artifact.
Visibility: Defender-side logs where collected
Required logs
- File-operation rates and process attribution
- Ransomware / DLP behavior alerts
- Canary files and recovery / backup audit
Coverage limit. A file-write burst is not proof of ransomware; in-process interpreters may not spawn a separate executable.
Custom-schema candidates, not out-of-box detectors. Map your application / cloud / platform logs to EventType, Actor, Asset, Action, Target and CorrelationId. KQL uses a custom OpenAttacksAudit_CL table; SPL uses openattacks:audit. EventType values are proposed normalization names, not native vendor event names. Correlation and environment-specific alert logic remain to be built.
Sigma
title: Hunt - Collection / encryption behavior
id: 0b1098da-0957-4f77-a2a4-e89a5a2e1a36
status: experimental
description: A process rapidly enumerates or modifies sensitive files and is
followed by encryption, export or a ransom-related artifact.
author: MagicSword OpenAttacks catalog
date: 2026-10-23
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: application
product: openattacks_audit
definition: Custom normalized audit schema; map EventType, Actor, Asset, Action,
Target and CorrelationId from the required source logs first.
detection:
selection:
EventType:
- file.bulk.modify
- data.export
condition: selection
KQL
// SCHEMA TEMPLATE: create/map this custom table before use; not a built-in Sentinel table.
// OpenAttacksAudit_CL: TimeGenerated(datetime), EventType/Actor/Asset/Action/Target/CorrelationId(string).
// Selects candidates only. Apply the stage hypothesis and correlation steps before alerting.
OpenAttacksAudit_CL
| where TimeGenerated > ago(7d)
| where EventType in ("file.bulk.modify", "data.export")
| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId
| order by TimeGenerated descSPL
sourcetype="openattacks:audit"
EventType IN ("file.bulk.modify", "data.export")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _timeInvestigation steps
- Correlate file bursts, extension changes and outbound transfer to the same process and identity.
- Validate against bulk backup / archiving activity and preserve the research-only qualification of a PoC.
Technical detailsTooling, impact & MITRE ATLAS
Attack context
- AI's role
- AI as operator
Tooling as reported
AI products, models and artifacts
- AI-driven command loop (model unspecified)
Other tooling
- 3AM ransomware
- Numbered retry scripts (av_remove2, av_remove3)
- Probe files (da_proof.txt, psexec-ok)
- Backdoor accounts (library, svc_bkpmon)
- Registry staging (HKLM\SOFTWARE\FIN001)
- PsExec
- comsvcs.dll
Targets and reported impact
- Targets / sectors
- UK schools
- Reported scale / exposure
- Multiple UK schools targeted; exact count unknown
- Target geography
- United Kingdom
United Kingdom reflects targeted school systems
Reported attribution
3AM ransomware affiliate
Activity timeline
- First seen
- 2026-10-01
- Last updated
- 2026-11-05
Updates
- 2026-11-04 — Bitdefender
3AM ransomware AI loop attack against UK schools disclosed
Source defensive notes
Detect model-style command syntax errors; monitor for numbered retry scripts; alert on probe files in unusual locations; review backdoor account creation; monitor registry key HKLM\SOFTWARE\FIN001; detect PsExec lateral movement; hunt for comsvcs.dll credential dumping
MITRE ATLAS
AI-specific catalog annotations based on the reported behavior; these are not MITRE case-study assignments.
AI loop autonomously executed attack commands with observable model errors and iteration patterns Source
Sources & research credit
1 sourceResearch by Marius Baciu, Adrian Schipor, Martin Zugec · Bitdefender
Relevant detection rules: - Sigma: Suspicious LSASS Process Access (comsvcs.dll dump pattern) (https://github.com/SigmaHQ/sigma/blob/master/rules/windows/process_creation/proc_creation_win_sysinternals_procdump_lsass.yml) - Sigma: Process Memory Dump Via Comsvcs.DLL (https://github.com/SigmaHQ/sigma/blob/master/rules/windows/process_creation/proc_creation_win_rundll32_process_dump_via_comsvcs.yml) - Monitor for registry key creation under HKLM\SOFTWARE\FIN001 - Detect backdoor account creation (library, svc_bkpmon) - Alert on numbered retry scripts (av_remove2, av_remove3 patterns) - Monitor for probe files (da_proof.txt, psexec-ok) in unusual locations - Detect command syntax errors indicating automated generation (Bash escapes in Windows commands) - LOLBAS references: comsvcs.dll (https://lolbas-project.github.io/lolbas/Libraries/Comsvcs/), PsExec (https://lolbas-project.github.io/lolbas/OtherMSBinaries/PsExec/) - Note: AI-generated command errors and iteration patterns require custom detection logic analyzing command line syntax anomalies.
Record & downloads
- Source record name
- 3AM ransomware affiliate using AI loop against UK schools
- Entry ID
- bitdefender-3am-ransomware-ai-2026
- Catalog review
- November 5, 2026
- AI-role confidence
- high