| ID | Name |
|---|---|
| T1070.001 | Clear Windows Event Logs |
| T1070.002 | Clear Linux or Mac System Logs |
| T1070.003 | Clear Command History |
| T1070.004 | File Deletion |
| T1070.005 | Network Share Connection Removal |
| T1070.006 | Timestomp |
In addition to clearing system logs, an adversary may clear the command history of a compromised account to conceal the actions undertaken during an intrusion. Various command interpreters keep track of the commands users type in their terminal so that users can retrace what they've done.
On Linux and macOS, these command histories can be accessed in a few different ways. While logged in, this command history is tracked in a file pointed to by the environment variable HISTFILE. When a user logs off a system, this information is flushed to a file in the user's home directory called ~/.bash_history. The benefit of this is that it allows users to go back to commands they've used before in different sessions.
Adversaries may delete their commands from these logs by manually clearing the history (history -c) or deleting the bash history file rm ~/.bash_history.
Adversaries may also leverage a Network Device CLI on network devices to clear command history data.[1]
On Windows hosts, PowerShell has two different command history providers: the built-in history and the command history managed by the PSReadLine module. The built-in history only tracks the commands used in the current session. This command history is not available to other sessions and is deleted when the session ends.
The PSReadLine command history tracks the commands used in all PowerShell sessions and writes them to a file ($env:APPDATA\Microsoft\Windows\PowerShell\PSReadLine\ConsoleHost_history.txt by default). This history file is available to all sessions and contains all past history since the file is not deleted when the session ends.[2]
Adversaries may run the PowerShell command Clear-History to flush the entire command history from a current PowerShell session. This, however, will not delete/flush the ConsoleHost_history.txt file. Adversaries may also delete the ConsoleHost_history.txt file or edit its contents to hide PowerShell commands they have run.[3][4]
| ID | Name | Description |
|---|---|---|
| G0096 | APT41 |
APT41 attempted to remove evidence of some of its activity by deleting Bash histories.[5] |
| S0601 | Hildegard |
Hildegard has used history -c to clear script shell logs.[6] |
| S0641 | Kobalos |
Kobalos can remove all command history on compromised hosts.[7] |
| G0032 | Lazarus Group |
Lazarus Group has routinely deleted log files on a compromised router, including automatic log deletion through the use of the logrotate utility.[8] |
| G0045 | menuPass |
menuPass has used Wevtutil to remove PowerShell execution logs.[9] |
| G0139 | TeamTNT |
| ID | Mitigation | Description |
|---|---|---|
| M1039 | Environment Variable Permissions |
Making the environment variables associated with command history read only may ensure that the history is preserved.[11] |
| M1029 | Remote Data Storage |
Forward logging of historical data to remote data store and centralized logging solution to preserve historical command line log data. |
| M1022 | Restrict File and Directory Permissions |
Preventing users from deleting or writing to certain files can stop adversaries from maliciously altering their |
| ID | Data Source | Data Component |
|---|---|---|
| DS0017 | Command | Command Execution |
| DS0022 | File | File Deletion |
| File Modification | ||
| DS0002 | User Account | User Account Authentication |
User authentication, especially via remote terminal services like SSH, without new entries in that user's ~/.bash_history is suspicious. Additionally, the removal/clearing of the ~/.bash_history file can be an indicator of suspicious activity.
Monitor for suspicious modifications or deletion of ConsoleHost_history.txt and use of the Clear-History command.