> For the complete documentation index, see [llms.txt](https://dmcxblue.gitbook.io/red-team-notes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dmcxblue.gitbook.io/red-team-notes/detection/execution.md). # Execution In this category we are aware that we need to Execute our Code, for whatever purpose it can be. Reverse Shell, Enumeration, Privesc, etc. But in this section we are a Hunter (Blue Team) and we are searching for our Prey (Red Team) again, what is left behind, what processes are created so they can reach their goal, what can we find so we know that they were here. This also helps us in to be more Opsec Safe Red Team can learn from here on what they are leaving behind and how can they avoid it in any way. Will focus in the common techniques explained in the Offensive Section: * MSHTA * PowerShell * RunDLL32 * Scheduled Tasks * Scripting * Trusted Developer Utilities * MSBuild * Regsvr32 * WinRm * WMIC * Etc --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://dmcxblue.gitbook.io/red-team-notes/detection/execution.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.