Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cyberstrikeus/T1036.009_break-process-trees
An adversary may attempt to evade process tree-based analysis by modifying executed malware's parent process ID (PPID).
Passed 19 of 22 test cases with the skill, and 11 of 22 without it.
and 6 more in the full report
8 fixed11 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are compiling an incident investigation sheet for malware detaching via daemon syscalls on Linux. What CWE title corresponds to the CWE category mapped to this defense evasion technique?
| Checked | Without skill | With skill |
|---|---|---|
| The response specifies Protection Mechanism Failure as the CWE title. | Missed | Passed |
The instructions your model reads when the skill loads.
Sub-technique of: T1036
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.
Another example is using the “daemon” syscall to detach from the current parent process and run in the background.
Platforms: Linux, macOS
Identify Attack Surface: Determine if the target environment is susceptible to Break Process Trees by examining the target platforms (Linux, macOS).
Assess Existing Defenses: Review whether mitigations for T1036.009 are in place. If defenses are absent or misconfigured, this technique may be exploitable.
Execute Test: Use tools and methods described in the MITRE ATT&CK page and external references below.
Note: No Atomic Red Team tests available for this technique. See Atomic Red Team GitHub for updates.
No specific mitigations documented for this technique.
test cases passed, vs 11 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.