Detection: Linux Possible Append Command To Profile Config File

Description

The following analytic detects suspicious command-lines that modify user profile files to automatically execute scripts or executables upon system reboot. It leverages data from Endpoint Detection and Response (EDR) agents, focusing on command-line executions involving profile files like ~/.bashrc and /etc/profile. This activity is significant as it indicates potential persistence mechanisms used by adversaries to maintain access to compromised hosts. If confirmed malicious, this could allow attackers to execute arbitrary code upon reboot, leading to persistent control over the system and potential further exploitation.

Search

 1
 2| tstats `security_content_summariesonly`
 3  count min(_time) as firstTime
 4        max(_time) as lastTime
 5
 6FROM datamodel=Endpoint.Processes WHERE
 7
 8Processes.process = "*echo*"
 9(
10    Processes.process IN ("*/home/*", "*~/*", "*/etc/*")
11    Processes.process IN (
12        "*/.bash_login*",
13        "*/.bash_logout*",
14        "*/.bash_profile*",
15        "*/.bashrc*",
16        "*/.profile*",
17        "*/profile*"
18    )
19    OR
20    (
21        Processes.process_current_directory = "/home/*"
22        Processes.process IN (
23            "*.bash_login*",
24            "*.bash_logout*",
25            "*.bash_profile*",
26            "*.bashrc*",
27            "*.profile*",
28            "* profile*"
29        )
30    )
31)
32
33BY Processes.action Processes.dest Processes.original_file_name
34   Processes.parent_process Processes.parent_process_exec Processes.parent_process_guid
35   Processes.parent_process_id Processes.parent_process_name Processes.parent_process_path
36   Processes.process_current_directory Processes.process Processes.process_exec Processes.process_guid
37   Processes.process_hash Processes.process_id Processes.process_integrity_level
38   Processes.process_name Processes.process_path Processes.user
39   Processes.user_id Processes.vendor_product
40
41| `drop_dm_object_name(Processes)`
42
43| `security_content_ctime(firstTime)`
44
45| `security_content_ctime(lastTime)`
46
47| `linux_possible_append_command_to_profile_config_file_filter`

Data Source

Name	Platform	Sourcetype	Source
Sysmon for Linux EventID 1	Linux	'sysmon:linux'	'Syslog:Linux-Sysmon/Operational'

Macros Used

Annotations

Default Configuration

This detection is configured by default in Splunk Enterprise Security to run with the following settings:

Implementation

The detection is based on data that originates from Endpoint Detection and Response (EDR) agents. These agents are designed to provide security-related telemetry from the endpoints where the agent is installed. To implement this search, you must ingest logs that contain the process GUID, process name, and parent process. Additionally, you must ingest complete command-line executions. These logs must be processed using the appropriate Splunk Technology Add-ons that are specific to the EDR product. The logs must also be mapped to the Processes node of the Endpoint data model. Use the Splunk Common Information Model (CIM) to normalize the field names and speed up the data modeling process.

Known False Positives

Administrator or network operator can use this commandline for automation purposes. Please update the filter macros to remove false positives.

Associated Analytic Story

• Linux Privilege Escalation

• Linux Persistence Techniques

Intermediate Findings

Threat Objects

References

• https://unix.stackexchange.com/questions/129143/what-is-the-purpose-of-bashrc-and-how-does-it-work

• https://attack.mitre.org/techniques/T1546/004/

Detection Testing

Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

Source: GitHub |

Version: 12