Cross-source coverage

T1564.011 / ATT&CK

Hide Artifacts: Ignore Process Interrupts

1 rule across 1 source.

From MITRE ATT&CK 20.1

Adversaries may evade defensive mechanisms by executing commands that hide from process interrupt signals. Many operating systems use signals to deliver messages to control process behavior. Command interpreters often include specific commands/flags that ignore errors and other hangups, such as when the user of the active session logs off. These interrupt signals may also be used by defensive tools and/or analysts to pause or terminate specified running processes.

Adversaries may invoke processes using nohup, PowerShell -ErrorAction SilentlyContinue, or similar commands that may be immune to hangups. This may enable malicious commands and malware to continue execution through system events that would otherwise terminate its execution, such as users logging off or the termination of its C2 network connection.

Hiding from process interrupt signals may allow malware to continue execution, but unlike Trap this does not establish Persistence since the process will not be re-invoked once actually terminated.

Tactics
Stealth
Platforms
Linux · macOS · Windows
Telemetry
auditd:SYSCALLWinEventLog:PowerShellWinEventLog:Sysmonmacos:unifiedlog

How MITRE says to detect it DET0067

Detection Strategy for Ignore Process Interrupts

Linux Analytic 0181

Execution of processes using nohup or shell redirection to ignore SIGHUP and continue running after session termination. Defender perspective: correlation between commands including nohup, disowned jobs, or `&` suffix with continued process execution after parent terminal exit.

  • auditd:SYSCALL execve call including 'nohup' or trailing '&'
  • auditd:SYSCALL process persists beyond parent shell termination

Windows Analytic 0182

PowerShell or script execution with parameters that suppress errors or ignore user interrupts, such as `-ErrorAction SilentlyContinue`. Defender perspective: detecting discrepancies between suppressed error arguments and continued execution behavior.

  • WinEventLog:PowerShell EventCode=4103, 4104, 4105, 4106
  • WinEventLog:Sysmon EventCode=1

macOS Analytic 0183

Use of nohup, disown, or AppleScript constructs to suppress process interrupts. Defender perspective: commands containing nohup or hidden background tasks (`osascript` with persistent execution) correlated with processes surviving user logouts.

  • macos:unifiedlog nohup, disown, or osascript execution patterns
  • macos:unifiedlog background process persists beyond user logout

elastic/protections-artifacts

1 rule
Detection Severity Format
Nohup Execution followed by Outbound Network Connection Undefined Elastic TOML

Detection rules belong to the projects that publish them and remain under their own licenses. This site indexes and links to them; it claims no rights in them.