Deletes administrator accounts in victim networks prior to encryption.1
Account Access Removal T1531
- Tactic
- Impact
- Platforms
- Linux, macOS, Windows, SaaS, IaaS, Office Suite, ESXi
- Version
- 1.5
- Created
- 09 October 2019
- Last modified
- 24 October 2025
- Contributors
- Hubert Mank; Arun Seelagan, CISA; Liran Ravich, CardinalOps
Adversaries may interrupt availability of system and network resources by inhibiting access to accounts utilized by legitimate users. Accounts may be deleted, locked, or manipulated (ex: changed credentials, revoked permissions for SaaS platforms such as Sharepoint) to remove access to accounts.[1] Adversaries may also subsequently log off and/or perform a System Shutdown/Reboot to set malicious changes into place.[2][3]
Account Access Removal MITRE reference T1531
2 groups have been recorded using this technique. Newest first; each entry carries MITRE’s procedure text and a link to the group’s full record. Click a name to filter the rules below.
Has removed a targeted organization's global admin accounts to lock the organization out of all access.1
All 2 groups for this technique
4 software entries are documented implementing this technique. MITRE files each as a tool or as malware; newest first, then by how many groups carry them.
Changes the password for local and domain users via net.exe to a random 32 character string to prevent these accounts from logging on. Additionally, DEADWOOD will terminate the winlogon.exe process to prevent attempts to log on to the infected system.1
Has the ability to change the password of local users on compromised hosts and can log off users.1
Has changed user account passwords and logged users off the system.1
Has been observed changing account passwords and logging off current users.12
All 4 software entries for this technique
Offense vs defense T1531
Is defensive coverage keeping up with adversary use? Eight counts, each ranked against all 697 ATT&CK techniques. Attack sits left, defense right, so a shape leaning left means adversaries are better documented here than defenders are equipped. Hover any spoke for its percentile and the share of techniques that have more. The timeline below shows when each side arrived.
How it got here
Adversary activity (campaign spans) over cumulative rule output. Each source is plotted independently from zero, so neither line includes the other. Campaign dates are year-granularity.
Account Access Removal detection strategy DET0120
MITRE names one behaviour worth catching for this technique and breaks it into 6 analytics, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Account Access Removal via Multi-Platform Audit Correlation
AN0334 · Windows
Correlated user account modification (reset, disable, deletion) events with anomalous process lineage (e.g., PowerShell or net.exe from an interactive session), especially outside of IT admin change windows or by non-admin users.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| User Account ModificationDC0010 | WinEventLog:Security | EventCode=4723, 4724, 4740 |
| Process CreationDC0032 | WinEventLog:Sysmon | EventCode=1 |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| UserContext | Account performing the operation (e.g., Domain Admins vs. local users) |
| TimeWindow | Alert only on actions outside of maintenance windows |
| ParentProcessName | Detect suspicious process lineage (e.g., powershell.exe launching net.exe) |
AN0335 · Linux
Password changes or account deletions via 'passwd', 'userdel', or 'chage' preceded by interactive shell or remote command execution from non-privileged accounts.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| User Account AuthenticationDC0002 | NSM:Connections | Accepted password or publickey for user from remote IP |
| Process CreationDC0032 | auditd:SYSCALL | SYSCALL record where exe contains passwd/userdel/chage and auid != root |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| ExecPath | Binary path for passwd or userdel, which may vary by distro |
| NonRootUIDThreshold | Alert only if auid != root or expected service account |
AN0336 · macOS
Execution of dscl or sysadminctl commands to disable, delete, or modify users combined with anomalous process ancestry or terminal session launch.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| User Account AuthenticationDC0002 | macos:unifiedlog | successful sudo or authentication for account not normally associated with admin actions |
| Command ExecutionDC0064 | macos:unifiedlog | command includes dscl . delete or sysadminctl --deleteUser |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| CommandLinePattern | Allow variation in dscl/sysadminctl command structure |
| AnomalousUserFlag | Detect new or rarely seen users performing user removal |
AN0337 · ESXi
Invocation of esxcli 'system account remove' from vCLI, SSH, or vSphere API with anomalous user access or outside maintenance windows.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| User Account AuthenticationDC0002 | esxi:vpxa | user login from unexpected IP or non-admin user role |
| User Account DeletionDC0009 | esxi:hostd | method=RemoveUser or esxcli system account remove invocation |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| RemoteUserRole | ESXi role triggering the change (e.g., Administrator vs. Viewer) |
| ExpectedIPs | IP ranges authorized to conduct admin-level actions |
AN0338 · Office Suite
O365 UnifiedAuditLog entries for Remove-Mailbox or Set-Mailbox with account disable or delete actions correlated with suspicious login locations or MFA bypass.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| User Account AuthenticationDC0002 | m365:signinlogs | Sign-in from anomalous location or impossible travel condition |
| User Account DeletionDC0009 | m365:unified | Remove-Mailbox, Set-Mailbox |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| RoleAssignment | Determine if operation was delegated to expected admin group |
| GeoThreshold | Trigger on unusual geographic login sources |
AN0339 · SaaS
Deletion or disablement of user accounts in platforms like Okta, Salesforce, or Zoom with anomalies in admin session attributes or mass actions within short duration.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| User Account ModificationDC0010 | saas:okta | user.lifecycle.delete, user.account.lock |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| BulkActionThreshold | Trigger if multiple deletions occur within a short period |
| SessionDeviceType | Alert on deletions initiated from unfamiliar device contexts |
Tests from Atomic Red Team (MIT licence) · technique definition