> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/js-runtime-attempted-to-read-git-authentication-tokens.md).
# JS runtime attempted to read Git authentication tokens
### Synopsis
| Field | Value |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 1 Day |
| Required Data | XDR Agent |
| ATT\&CK Tactic | Credential Access (TA0006), Execution (TA0002) |
| ATT\&CK Technique | Command and Scripting Interpreter (T1059), Command and Scripting Interpreter: JavaScript (T1059.007), Unsecured Credentials (T1552) |
| Severity | Medium |
### Description
A JavaScript runtime was used to execute a .js file that attempted to read Git personal authentication tokens via the 'gh auth token' command. This behavior is associated with the Mini Shai Hulud campaign, where attackers use lightweight JS engines to execute malicious package code and steal developer credentials.
### Attacker's Goals
Steal Git personal authentication tokens to gain access to developer accounts and their associated repositories, enabling supply chain attacks.
### Investigative actions
* Investigate the .js file executed by the JS runtime and determine if it is part of a legitimate package.
* Check if the Git authentication tokens were successfully exfiltrated.
* Review the package that triggered the execution for known malicious indicators.
* Check for other signs of the Mini Shai Hulud campaign on the host.
### Variations
Uncommon JS runtime attempted to read Git authentication tokens
**Synopsis**
| Field | Value |
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006), Execution (TA0002) |
| ATT\&CK Technique | Command and Scripting Interpreter (T1059), Command and Scripting Interpreter: JavaScript (T1059.007), Unsecured Credentials (T1552) |
| Severity | High |
**Description**
A JavaScript runtime was used to execute a .js file that attempted to read Git personal authentication tokens via the 'gh auth token' command. This behavior is associated with the Mini Shai Hulud campaign, where attackers use lightweight JS engines to execute malicious package code and steal developer credentials.
**Attacker's Goals**
Steal Git personal authentication tokens to gain access to developer accounts and their associated repositories, enabling supply chain attacks.
**Investigative actions**
* Investigate the .js file executed by the JS runtime and determine if it is part of a legitimate package.
* Check if the Git authentication tokens were successfully exfiltrated.
* Review the package that triggered the execution for known malicious indicators.
* Check for other signs of the Mini Shai Hulud campaign on the host.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/js-runtime-attempted-to-read-git-authentication-tokens.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.