This repository was archived by the owner on Jan 29, 2020. It is now read-only.
Fixed so the agent should work on Windows 10 Pro Build 17134 #1334
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The changes should make the Empire agent to work again on Windows 10.
Tested on
Windows 10 Pro Build 17134
Windows 10 Home Build 17763
The change includes the following,
AMSI bypass, by Rasta Mouse (https://rastamouse.me)
HTTPS fix by https://github.com/zinzloun
Changed the stager and the agent so AMSI not trigger on "Invoke-Empire"
Changed the launcher so AMSI not trigger on "amsiInitFailed".