Clear Command History

T1070.003

Sub-technique of T1070 Indicator Removal.View on attack.mitre.org

About this technique

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 (clear logging and/or clear history). On ESXi servers, command history may be manually removed from the `/var/log/shell.log` file.

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.

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.

Detection rules11

Rules on DetectionCode tagged with T1070.003.

Sigma9

RuleLevelLog source
Cisco Clear Logshighcisco / NULL
Clearing Windows Console Historyhighwindows / ps_script
Disable Powershell Command Historyhighwindows / ps_script
Linux Command History Tamperinghighlinux / NULL
RunMRU Registry Key Deletionhighwindows / process_creation
RunMRU Registry Key Deletion - Registryhighwindows / registry_delete
Clear PowerShell History - PowerShellmediumwindows / ps_script
Clear PowerShell History - PowerShell Modulemediumwindows / ps_module
Suspicious IO.FileStreammediumwindows / ps_script

Splunk2

RuleTypeRiskData source
Windows ConsoleHost History File DeletionAnomalyNULLSysmon EventID 23, Sysmon EventID 26
Windows Powershell History File DeletionAnomalyNULLPowershell Script Block Logging 4104

Groups8

Software3

Campaigns0

None recorded.

Procedure examples11

Groups8

Used byProcedure example
GroupAPT41

APT41 attempted to remove evidence of some of its activity by deleting Bash histories.

GroupAPT5

APT5 has cleared the command history on targeted ESXi servers.

GroupAquatic Panda

Aquatic Panda cleared command history in Linux environments to remove traces of activity after operations.

GroupLazarus Group

Lazarus Group has routinely deleted log files on a compromised router, including automatic log deletion through the use of the logrotate utility.

GroupMagic Hound

Magic Hound has removed mailbox export requests from compromised Exchange servers.

GroupMedusa Group

Medusa Group has cleared command history by running the PowerShell command `Remove-Item (Get-PSReadlineOption).HistorySavePath`.

GroupmenuPass

menuPass has used Wevtutil to remove PowerShell execution logs.

GroupTeamTNT

TeamTNT has cleared command history with history -c.

Software3

Used byProcedure example
MalwareHildegard

Hildegard has used history -c to clear script shell logs.

MalwareJ-magic

J-magic can overwrite previously executed command line arguments.

MalwareKobalos

Kobalos can remove all command history on compromised hosts.

References5

  1. Broadcom ESXi Shell Audit Open source
    Broadcom. (2025, February 20). Auditing ESXi Shell logins and commands. Retrieved March 26, 2025.
  2. Microsoft PowerShell Command History Open source
    Microsoft. (2020, May 13). About History. Retrieved September 4, 2020.
  3. Sophos PowerShell Command History Forensics Open source
    Vikas, S. (2020, August 26). PowerShell Command History Forensics. Retrieved November 17, 2024.
  4. Sophos PowerShell command audit Open source
    jak. (2020, June 27). Live Discover - PowerShell command audit. Retrieved August 21, 2020.
  5. US-CERT-TA18-106A Open source
    US-CERT. (2018, April 20). Alert (TA18-106A) Russian State-Sponsored Cyber Actors Targeting Network Infrastructure Devices. Retrieved October 19, 2020.

Data from MITRE ATT&CK® (Enterprise). ATT&CK® is a registered trademark of The MITRE Corporation.