MediumSigmaHQ Sreeman

Potential Persistence Attempt Via Existing Service Tampering

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.

Detection logic

Detection requirements

Platform: Windows
The rule states no platform. This is derived from the 2 ATT&CK techniques it maps to.
Log source product: windows
Log source category: process_creation

Known benign triggers

Unknown

References

Links the source published beside this detection. Reference is the link the source wrote, unmodified. Class is decided by this catalogue from the host and path, not stated by the source. Cited by counts published detections citing the same resource, including this one, and the sources beneath it count the repositories this catalogue ingests, which is not the same as independent research.
Reference	Class	Cited by
pentestlab.blog/2020/01/22/persistence-modify-existing-service/	Unclassified	Only this detection cites it

Detection rules

Potential Persistence Attempt Via Existing Service Tampering

Detection logic

Detection requirements

Known benign triggers

MITRE ATT&CK mappings

References

From the source

Licence

Authorship

Detection rules