Empire is a PowerShell and Python post-exploitation agent.
 
 
Go to file
HarmJ0y 446a004cc1 Merge pull request #157 from PowerShellEmpire/restful_api
RESTful API
2016-03-22 14:15:25 -07:00
.github Added contribution and issue templates. 2016-03-19 06:52:59 -04:00
data Added trollsploit/rick_astley to run @SadProcessor's audio rickroll 2016-03-21 23:11:12 -04:00
lib Merge pull request #157 from PowerShellEmpire/restful_api 2016-03-22 14:15:25 -07:00
setup Added SSL and basic token auth to the RESTful API 2016-03-22 01:41:48 -04:00
.gitignore Initial BSidesLV '15 release of v1.0.0 2015-08-05 14:36:39 -04:00
LICENSE Initial BSidesLV '15 release of v1.0.0 2015-08-05 14:36:39 -04:00
README.md Empire 1.4 release. 2015-12-29 19:29:05 -05:00
changelog Updated changelog. 2016-02-17 22:37:25 -05:00
empire Moved empire-rest to empire 2016-03-22 17:06:18 -04:00

README.md

#Empire

Empire is a pure PowerShell post-exploitation agent built on cryptologically-secure communications and a flexible architecture. Empire implements the ability to run PowerShell agents without needing powershell.exe, rapidly deployable post-exploitation modules ranging from key loggers to Mimikatz, and adaptable communications to evade network detection, all wrapped up in a usability-focused framework. It premiered at BSidesLV in 2015.

To install, run the ./setup/install.sh script. There's also a quickstart here and full documentation here.

Empire relies heavily on the work from several other projects for its underlying functionality. We have tried to call out a few of those people we've interacted with heavily here and have included author/reference link information in the source of each Empire module as appropriate. If we have failed to improperly cite existing or prior work, please let us know.

Empire is developed by @harmj0y, @sixdub, and @enigma0x3.

Contribution Rules

Contributions are more than welcome! The more people who contribute to the project the better Empire will be for everyone. Below are a few guidelines for submitting contributions.

  • Submit pull requests to the dev branch. After testing, changes will be merged to master.
  • Base modules on the template at ./modules/template.py. Note that for some modules you may need to massage the output to get it into a nicely displayable text format with Out-String.
  • Cite previous work in the 'Comments' module section.
  • If your script.ps1 logic is large, may be reused by multiple modules, or is updated often, consider implementing the logic in the appropriate data/module_source/* directory and pulling the script contents into the module on tasking.
  • Use approved PowerShell verbs for any functions.
  • PowerShell Version 2 compatibility is STRONGLY preferred.
  • TEST YOUR MODULE! Be sure to run it from an Empire agent before submitting a pull to ensure everything is working correctly.
  • For additional guidelines for your PowerShell code itself, check out the PowerSploit style guide.