Exploit Pack - Documentation
  • Exploit Pack
    • Installation guide
    • License Activation
    • First steps
    • Running the network mapper
    • AutoPwn
    • UTF-8 Locator
    • Notepad
    • Reverse shell - One-liners
    • Hex Editor
    • GDB Connector
    • Log your actions
    • Exploits customization
    • Add a Proxy to Exploit Pack
    • Using Reverse Shells
    • XSS Agent - Tunnel
    • Advanced DLL Injections
    • VBS/PS Agent - Remote Access
    • VBS Agent Wizard
    • Exploit Development I
    • Exploit Development II
    • Exploit Development III
  • Control Pack
    • Installation guide
    • License Activation
    • First Steps: Configure Control Pack
    • Launch your first agent
    • Control Pack agent's code
    • Agent connection
    • Java Agent
    • Browser Agent
    • VBS Agent
    • .NET Profiler DLL Agent
    • How to use the DLL + UnHooker Agent
    • .NET shell
    • Python Shell
  • Kernel Pack
Powered by GitBook
On this page

Was this helpful?

  1. Control Pack

Launch your first agent

PreviousFirst Steps: Configure Control PackNextControl Pack agent's code

Last updated 1 year ago

Was this helpful?

As a first step, choose an agent from the Control Pack menu, your choice of agent should be determined by the specific target and the desired method of execution. For instance, opting for the Java agent will make it run from a JAR file, or you can convert this file to a PE (exe) file using Launch4J. This agent will run from the Java Virtual Machine and that makes it challenging, if not impossible, for an AV or EDR to trace the bytecode of this agent during runtime.

The type of access would also depend on the agent you run on your target. If you select a browser shell, your access will be confined to the context of the web browser, and for every agent type the agent will inherit from the user the rights and execution permissions. The communication stream used for all these agents is obfuscated over HTTP mimicking regular web traffic.