|T1036.001||Invalid Code Signature|
|T1036.003||Rename System Utilities|
|T1036.004||Masquerade Task or Service|
|T1036.005||Match Legitimate Name or Location|
|T1036.006||Space after Filename|
|T1036.007||Double File Extension|
|T1036.008||Masquerade File Type|
|T1036.009||Break Process Trees|
An adversary may attempt to evade process tree-based analysis by modifying executed malware's parent process ID (PPID). If endpoint protection software leverages the "parent-child" relationship for detection, breaking this relationship could result in the adversary’s behavior not being associated with previous process tree activity. On Unix-based systems breaking this process tree is common practice for administrators to execute software using scripts and programs.
On Linux systems, adversaries may execute a series of Native API calls to alter malware's process tree. For example, adversaries can execute their payload without any arguments, call the
fork() API call twice, then have the parent process exit. This creates a grandchild process with no parent process that is immediately adopted by the
init system process (PID 1), which successfully disconnects the execution of the adversary's payload from its previous process tree.
This type of attack technique cannot be easily mitigated with preventive controls since it is based on the abuse of system features.
|ID||Data Source||Data Component||Detects|
|DS0009||Process||OS API Execution||
Monitor for API calls such as
Monitor for the abnormal creation of background processes as well as processes executing from abnormal locations, such as