GitHub Authentication Token Access via Node.js

 1[metadata]
 2creation_date = "2025/09/18"
 3integration = ["endpoint"]
 4maturity = "production"
 5updated_date = "2025/09/18"
 6
 7[rule]
 8author = ["Elastic"]
 9description = """
10This rule detects when the Node.js runtime spawns a shell to execute the GitHub CLI (gh) command to retrieve
11a GitHub authentication token. The GitHub CLI is a command-line tool that allows users to interact with
12GitHub from the terminal. The "gh auth token" command is used to retrieve an authentication token for
13GitHub, which can be used to authenticate API requests and perform actions on behalf of the user. Adversaries
14may use this technique to access GitHub repositories and potentially exfiltrate sensitive information or
15perform malicious actions. This activity was observed in the wild as part of the Shai-Hulud worm.
16"""
17from = "now-9m"
18index = ["logs-endpoint.events.process*"]
19language = "eql"
20license = "Elastic License v2"
21name = "GitHub Authentication Token Access via Node.js"
22references = ["https://www.elastic.co/blog/shai-hulud-worm-npm-supply-chain-compromise"]
23risk_score = 47
24rule_id = "e5d69377-f8cf-4e8f-8328-690822cd012a"
25setup = """## Setup
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: Credential Access",
56    "Tactic: Discovery",
57    "Data Source: Elastic Defend",
58    "Resources: Investigation Guide",
59]
60timestamp_override = "event.ingested"
61type = "eql"
62query = '''
63process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and process.parent.name == "node" and
64process.name in ("bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish") and process.args == "gh auth token"
65'''
66
67[[rule.threat]]
68framework = "MITRE ATT&CK"
69
70[[rule.threat.technique]]
71id = "T1552"
72name = "Unsecured Credentials"
73reference = "https://attack.mitre.org/techniques/T1552/"
74
75[[rule.threat.technique]]
76id = "T1528"
77name = "Steal Application Access Token"
78reference = "https://attack.mitre.org/techniques/T1528/"
79
80[rule.threat.tactic]
81id = "TA0006"
82name = "Credential Access"
83reference = "https://attack.mitre.org/tactics/TA0006/"
84
85[[rule.threat]]
86framework = "MITRE ATT&CK"
87
88[[rule.threat.technique]]
89id = "T1613"
90name = "Container and Resource Discovery"
91reference = "https://attack.mitre.org/techniques/T1613/"
92
93[rule.threat.tactic]
94id = "TA0007"
95name = "Discovery"
96reference = "https://attack.mitre.org/tactics/TA0007/"