This documentation contains work-in-progress information for future Elastic Stack and Cloud releases. Use the version selector to view supported release docs. It also contains some Elastic Cloud serverless information. Check out our serverless docs for more details.
« Potential Persistence via Periodic Tasks Screensaver Plist File Modified by Unexpected Process »
Elastic Docs ›Elastic Security Solution [8.x] ›Downloadable rule update v8.4.2

Unexpected Child Process of macOS Screensaver Engine

edit

Unexpected Child Process of macOS Screensaver Engine

edit

Identifies when a child process is spawned by the screensaver engine process, which is consistent with an attacker’s malicious payload being executed after the screensaver activated on the endpoint. An adversary can maintain persistence on a macOS endpoint by creating a malicious screensaver (.saver) file and configuring the screensaver plist file to execute code each time the screensaver is activated.

Rule type: eql

Rule indices:

  • auditbeat-*
  • logs-endpoint.events.*

Severity: medium

Risk score: 47

Runs every: 5m

Searches indices from: now-9m (Date Math format, see also Additional look-back time)

Maximum alerts per execution: 100

References:

Tags:

  • Elastic
  • Host
  • macOS
  • Threat Detection
  • Persistence

Version: 101

Rule authors:

  • Elastic

Rule license: Elastic License v2

Investigation guide

edit
## Triage and analysis

- Analyze the descendant processes of the ScreenSaverEngine process for malicious code and suspicious behavior such
as a download of a payload from a server.
- Review the installed and activated screensaver on the host. Triage the screensaver (.saver) file that was triggered to
identify whether the file is malicious or not.

Rule query

edit
process where event.type == "start" and process.parent.name == "ScreenSaverEngine"

Framework: MITRE ATT&CKTM

« Potential Persistence via Periodic Tasks Screensaver Plist File Modified by Unexpected Process »