Suspicious APT Package Manager Network Connection

  1[metadata]
  2creation_date = "2024/02/01"
  3integration = ["endpoint"]
  4maturity = "production"
  5updated_date = "2024/09/23"
  6
  7[rule]
  8author = ["Elastic"]
  9description = """
 10Detects suspicious network events executed by the APT package manager, potentially indicating persistence through an APT
 11backdoor. In Linux, APT (Advanced Package Tool) is a command-line utility used for handling packages on Debian-based
 12systems, providing functions for installing, updating, upgrading, and removing software along with managing package
 13repositories. Attackers can backdoor APT to gain persistence by injecting malicious code into scripts that APT runs,
 14thereby ensuring continued unauthorized access or control each time APT is used for package management.
 15"""
 16from = "now-9m"
 17index = ["logs-endpoint.events.*"]
 18language = "eql"
 19license = "Elastic License v2"
 20name = "Suspicious APT Package Manager Network Connection"
 21references = ["https://www.elastic.co/security-labs/sequel-on-persistence-mechanisms"]
 22risk_score = 47
 23rule_id = "eaef8a35-12e0-4ac0-bc14-81c72b6bd27c"
 24setup = """## Setup
 25
 26
 27This rule requires data coming in from Elastic Defend.
 28
 29### Elastic Defend Integration Setup
 30Elastic 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.
 31
 32#### Prerequisite Requirements:
 33- Fleet is required for Elastic Defend.
 34- To configure Fleet Server refer to the [documentation](https://www.elastic.co/guide/en/fleet/current/fleet-server.html).
 35
 36#### The following steps should be executed in order to add the Elastic Defend integration on a Linux System:
 37- Go to the Kibana home page and click "Add integrations".
 38- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
 39- Click "Add Elastic Defend".
 40- Configure the integration name and optionally add a description.
 41- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
 42- 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).
 43- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
 44- 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.
 45For more details on Elastic Agent configuration settings, refer to the [helper guide](https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html).
 46- Click "Save and Continue".
 47- 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.
 48For more details on Elastic Defend refer to the [helper guide](https://www.elastic.co/guide/en/security/current/install-endpoint.html).
 49"""
 50severity = "medium"
 51tags = [
 52    "Domain: Endpoint",
 53    "OS: Linux",
 54    "Use Case: Threat Detection",
 55    "Tactic: Persistence",
 56    "Tactic: Command and Control",
 57    "Tactic: Defense Evasion",
 58    "Data Source: Elastic Defend",
 59]
 60type = "eql"
 61
 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  [network where host.os.type == "linux" and event.action == "connection_attempted" and event.type == "start" and not (
 70     destination.ip == null or destination.ip == "0.0.0.0" or cidrmatch(
 71     destination.ip, "10.0.0.0/8", "127.0.0.0/8", "169.254.0.0/16", "172.16.0.0/12", "192.0.0.0/24", "192.0.0.0/29",
 72     "192.0.0.8/32", "192.0.0.9/32", "192.0.0.10/32", "192.0.0.170/32", "192.0.0.171/32", "192.0.2.0/24",
 73     "192.31.196.0/24", "192.52.193.0/24", "192.168.0.0/16", "192.88.99.0/24", "224.0.0.0/4", "100.64.0.0/10",
 74     "192.175.48.0/24","198.18.0.0/15", "198.51.100.0/24", "203.0.113.0/24", "240.0.0.0/4", "::1", "FE80::/10",
 75     "FF00::/8", "172.31.0.0/16"
 76     )
 77   ) and not process.executable == "/usr/bin/apt-listbugs"
 78  ] by process.parent.entity_id
 79'''
 80
 81
 82[[rule.threat]]
 83framework = "MITRE ATT&CK"
 84[[rule.threat.technique]]
 85id = "T1543"
 86name = "Create or Modify System Process"
 87reference = "https://attack.mitre.org/techniques/T1543/"
 88
 89[[rule.threat.technique]]
 90id = "T1546"
 91name = "Event Triggered Execution"
 92reference = "https://attack.mitre.org/techniques/T1546/"
 93[[rule.threat.technique.subtechnique]]
 94id = "T1546.016"
 95name = "Installer Packages"
 96reference = "https://attack.mitre.org/techniques/T1546/016/"
 97
 98
 99[[rule.threat.technique]]
100id = "T1574"
101name = "Hijack Execution Flow"
102reference = "https://attack.mitre.org/techniques/T1574/"
103
104
105[rule.threat.tactic]
106id = "TA0003"
107name = "Persistence"
108reference = "https://attack.mitre.org/tactics/TA0003/"
109[[rule.threat]]
110framework = "MITRE ATT&CK"
111
112[rule.threat.tactic]
113id = "TA0011"
114name = "Command and Control"
115reference = "https://attack.mitre.org/tactics/TA0011/"
116[[rule.threat]]
117framework = "MITRE ATT&CK"
118
119[rule.threat.tactic]
120id = "TA0005"
121name = "Defense Evasion"
122reference = "https://attack.mitre.org/tactics/TA0005/"