Potential Persistence Attempt Via Existing Service Tampering
Last updated on:
In this page
About the rule
Rule Type
Standard
Rule Description
Detects the modification of an existing service in order to execute an arbitrary payload when the service is started or killed as a potential method for persistence.
Severity
Trouble
Rule Requirement
Criteria
Action1:
actionname = "Process started" AND ((COMMANDLINE contains "sc " AND COMMANDLINE contains "config " AND COMMANDLINE contains "binpath=") OR (COMMANDLINE contains "sc " AND COMMANDLINE contains "failure" AND COMMANDLINE contains "command=")) OR (((COMMANDLINE contains "reg " AND COMMANDLINE contains "add " AND COMMANDLINE contains "FailureCommand") OR (COMMANDLINE contains "reg " AND COMMANDLINE contains "add " AND COMMANDLINE contains "ImagePath")) AND COMMANDLINE contains ".sh,.exe,.dll,.bin$,.bat,.cmd,.js,.msh$,.reg$,.scr,.ps,.vb,.jar,.pl")
select Action1.HOSTNAME,Action1.MESSAGE,Action1.COMMANDLINE,Action1.FILE_NAME,Action1.PROCESSNAME,Action1.USERNAME,Action1.PARENTPROCESSNAME,Action1.DOMAIN,Action1.ORIGINALFILENAME,Action1.PARENTPROCESSID,Action1.PROCESSID,Action1.PRODUCT_NAME,Action1.SECURITYID
Detection
Execution Mode
realtime
Log Sources
Windows
Author
Sreeman
