fix: optimize "Invoke-Sharp" coverage
This commit is contained in:
@@ -166,43 +166,7 @@ detection:
|
||||
- 'Invoke-Seatbelt'
|
||||
- 'Invoke-ServiceAbuse'
|
||||
- 'Invoke-ShadowSpray'
|
||||
- 'Invoke-SharpAllowedToAct'
|
||||
- 'Invoke-SharpBlock'
|
||||
- 'Invoke-SharpBypassUAC'
|
||||
- 'Invoke-SharpChromium'
|
||||
- 'Invoke-SharpClipboard'
|
||||
- 'Invoke-SharpCloud'
|
||||
- 'Invoke-SharpDPAPI'
|
||||
- 'Invoke-SharpDump'
|
||||
- 'Invoke-SharPersist'
|
||||
- 'Invoke-SharpGPOAbuse'
|
||||
- 'Invoke-SharpGPO-RemoteAccessPolicies'
|
||||
- 'Invoke-SharpHandler'
|
||||
- 'Invoke-SharpHide'
|
||||
- 'Invoke-Sharphound' # Also Covers "Invoke-SharpHound2", "Invoke-SharpHound3"...etc.
|
||||
- 'Invoke-SharpImpersonation'
|
||||
- 'Invoke-SharpImpersonationNoSpace'
|
||||
- 'Invoke-SharpKatz'
|
||||
- 'Invoke-SharpLdapRelayScan'
|
||||
- 'Invoke-Sharplocker'
|
||||
- 'Invoke-SharpLoginPrompt'
|
||||
- 'Invoke-SharpMove'
|
||||
- 'Invoke-SharpPrinter'
|
||||
- 'Invoke-SharpPrintNightmare'
|
||||
- 'Invoke-SharpRDP'
|
||||
- 'Invoke-SharpSCCM'
|
||||
- 'Invoke-SharpSecDump'
|
||||
- 'Invoke-Sharpshares'
|
||||
- 'Invoke-SharpSniper'
|
||||
- 'Invoke-SharpSploit'
|
||||
- 'Invoke-SharpSpray'
|
||||
- 'Invoke-SharpSSDP'
|
||||
- 'Invoke-SharpStay'
|
||||
- 'Invoke-SharpUp'
|
||||
- 'Invoke-Sharpview'
|
||||
- 'Invoke-SharpWatson'
|
||||
- 'Invoke-Sharpweb'
|
||||
- 'Invoke-SharpWSUS'
|
||||
- 'Invoke-Sharp' # Covers all "Invoke-Sharp" variants
|
||||
- 'Invoke-Shellcode'
|
||||
- 'Invoke-SMBScanner'
|
||||
- 'Invoke-Snaffler'
|
||||
|
||||
Reference in New Issue
Block a user