Startup or Run Key Registry Modification
Identifies run key or startup key registry modifications. In order to survive reboots and other system interrupts, attackers will modify run keys within the registry or leverage startup folder items as a form of…
Description
Identifies run key or startup key registry modifications. In order to survive reboots and other system interrupts, attackers will modify run keys within the registry or leverage startup folder items as a form of persistence.
Detection logic
Its licence does not clear it for publishing here
Sunturai publishes a detection's own text where the licence it arrived under has been reviewed and permits it, and Elastic License 2.0 has not. The query as its source wrote it, its canonical form and the hash that pins this revision are in the workspace record.
Detection requirements
- Platform
- LinuxmacOSNetwork DevicesWindows
The rule states no platform. This is derived from the 2 ATT&CK techniques it maps to.
- Log source category
- event_index
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| www.elastic.co/security-labs/elastic-security-uncovers-blister-malware-campaign | 5 |
From the source
- At source
- Open at source
- Upstream identifier
- 97fc44d3-8dae-4019-ae83-298c3015600f
- Tagged by the source as
- Data Source: Elastic DefendData Source: Elastic EndgameDomain: EndpointNoise: MediumOS: WindowsPerformance: NormalPlatform: WindowsResources: Investigation GuideResources: OsqueryRule Type: Event Correlation (EQL)Tactic: PersistenceUse Case: Threat Detection
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Oct 6, 2026
- Version
- 4