Suspicious APT Package Manager Execution

  1[metadata]
  2creation_date = "2024/02/01"
  3maturity = "production"
  4min_stack_comments = "New fields added: required_fields, related_integrations, setup"
  5min_stack_version = "8.3.0"
  6updated_date = "2024/03/08"
  7integration = ["endpoint"]
  8
  9[rule]
 10author = ["Elastic"]
 11description = """
 12Detects suspicious process events executed by the APT package manager, potentially indicating persistence through an APT
 13backdoor. In Linux, APT (Advanced Package Tool) is a command-line utility used for handling packages on Debian-based
 14systems, providing functions for installing, updating, upgrading, and removing software along with managing package
 15repositories. Attackers can backdoor APT to gain persistence by injecting malicious code into scripts that APT runs,
 16thereby ensuring continued unauthorized access or control each time APT is used for package management.
 17"""
 18from = "now-9m"
 19index = ["logs-endpoint.events.*"]
 20language = "eql"
 21license = "Elastic License v2"
 22name = "Suspicious APT Package Manager Execution"
 23risk_score = 47
 24rule_id = "ad959eeb-2b7b-4722-ba08-a45f6622f005"
 25setup = """## Setup
 26
 27
 28This rule requires data coming in from Elastic Defend.
 29
 30### Elastic Defend Integration Setup
 31Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
 32
 33#### Prerequisite Requirements:
 34- Fleet is required for Elastic Defend.
 35- To configure Fleet Server refer to the [documentation](https://www.elastic.co/guide/en/fleet/current/fleet-server.html).
 36
 37#### The following steps should be executed in order to add the Elastic Defend integration on a Linux System:
 38- Go to the Kibana home page and click "Add integrations".
 39- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
 40- Click "Add Elastic Defend".
 41- Configure the integration name and optionally add a description.
 42- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
 43- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. [Helper guide](https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html).
 44- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
 45- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
 46For more details on Elastic Agent configuration settings, refer to the [helper guide](https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html).
 47- Click "Save and Continue".
 48- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
 49For more details on Elastic Defend refer to the [helper guide](https://www.elastic.co/guide/en/security/current/install-endpoint.html).
 50"""
 51severity = "medium"
 52tags = [
 53        "Domain: Endpoint",
 54        "OS: Linux",
 55        "Use Case: Threat Detection",
 56        "Tactic: Persistence",
 57        "Tactic: Execution",
 58        "Tactic: Defense Evasion",
 59        "Data Source: Elastic Defend"
 60        ]
 61type = "eql"
 62query = '''
 63sequence by host.id with maxspan=5s
 64  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and
 65   process.parent.name == "apt" and process.args == "-c" and process.name in (
 66     "bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish"
 67   )
 68  ] by process.entity_id
 69  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and process.name : (
 70     "bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish", "python*", "php*",
 71     "perl", "ruby", "lua*", "openssl", "nc", "netcat", "ncat", "telnet", "awk"
 72   )
 73  ] by process.parent.entity_id
 74'''
 75
 76[[rule.threat]]
 77framework = "MITRE ATT&CK"
 78
 79[[rule.threat.technique]]
 80id = "T1543"
 81name = "Create or Modify System Process"
 82reference = "https://attack.mitre.org/techniques/T1543/"
 83
 84[[rule.threat.technique]]
 85id = "T1574"
 86name = "Hijack Execution Flow"
 87reference = "https://attack.mitre.org/techniques/T1574/"
 88
 89[rule.threat.tactic]
 90id = "TA0003"
 91name = "Persistence"
 92reference = "https://attack.mitre.org/tactics/TA0003/"
 93
 94[[rule.threat]]
 95framework = "MITRE ATT&CK"
 96
 97[rule.threat.tactic]
 98name = "Execution"
 99id = "TA0002"
100reference = "https://attack.mitre.org/tactics/TA0002/"
101
102[[rule.threat.technique]]
103id = "T1059"
104name = "Command and Scripting Interpreter"
105reference = "https://attack.mitre.org/techniques/T1059/"
106
107[[rule.threat.technique.subtechnique]]
108id = "T1059.004"
109name = "Unix Shell"
110reference = "https://attack.mitre.org/techniques/T1059/004/"
111
112[[rule.threat]]
113framework = "MITRE ATT&CK"
114
115[rule.threat.tactic]
116id = "TA0005"
117name = "Defense Evasion"
118reference = "https://attack.mitre.org/tactics/TA0005/"