We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
$profile | fl -Force
List the following if these files exist using a new category named PSProfiles
AllUsersAllHosts : C:\Windows\System32\WindowsPowerShell\v1.0\profile.ps1 AllUsersCurrentHost : C:\Windows\System32\WindowsPowerShell\v1.0\Microsoft.PowerShell_profile.ps1 CurrentUserAllHosts : C:\Users\local-user\Documents\WindowsPowerShell\profile.ps1 CurrentUserCurrentHost : C:\Users\local-user\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1
They are not considered as a persistence mechanism...
> $PSVersionTable Name Value ---- ----- PSVersion 5.1.16299.248 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...} BuildVersion 10.0.16299.248 CLRVersion 4.0.30319.42000 WSManStackVersion 3.0 PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1
The text was updated successfully, but these errors were encountered:
Adding PowerShell profiles issue #12
9b5d80b
It may not be exhaustive because it depends on the host. It's currently better than nothing.
Sorry, something went wrong.
http://www.exploit-monday.com/2015/11/investigating-subversive-powershell.html
No branches or pull requests
Steps to reproduce
Expected behavior
List the following if these files exist using a new category named PSProfiles
Actual behavior
They are not considered as a persistence mechanism...
Environment data
The text was updated successfully, but these errors were encountered: