Has searched through target companies’ GitHub repositories for login credentials or API keys.1
Code Repositories T1593.003
- Tactic
- Reconnaissance
- Platform
- PRE
- Version
- 1.0
- Created
- 09 August 2022
- Last modified
- 12 May 2026
- Contributors
- Matt Burrough, @mattburrough, Microsoft; Vinayak Wadhwa, SAFE Security
Adversaries may search public code repositories for information about victims that can be used during targeting. Victims may store code in repositories on various third-party websites such as GitHub, GitLab, SourceForge, and BitBucket. Users typically interact with code repositories through a web application or command-line utilities such as git.
Code Repositories MITRE reference T1593.003
4 groups have been recorded using this technique. Newest first; each entry carries MITRE’s procedure text and a link to the group’s full record. Click a name to filter the rules below.
Had identified and solicited victims through code repositories such as GitHub.1
Has searched public code repositories for exposed credentials.1
Has discovered leaked corporate credentials on public repositories including GitHub.1
All 4 groups for this technique
1 software entry is documented implementing this technique. MITRE files each as a tool or as malware; newest first, then by how many groups carry them.
Has the ability to search open sites and code repositories for compromised credentials.12 Shai-Hulud has discovered packages associated with compromised accounts.3 Shai-Hulud has also searched code repositories for other compromised repositories that include predefined parameters or markers to include “Second Coming” combined with an 18-character alphanumeric string.3
All 1 software entries for this technique
Offense vs defense T1593.003
Is defensive coverage keeping up with adversary use? Eight counts, each ranked against all 697 ATT&CK techniques. Attack sits left, defense right, so a shape leaning left means adversaries are better documented here than defenders are equipped. Hover any spoke for its percentile and the share of techniques that have more. The timeline below shows when each side arrived.
How it got here
Adversary activity (campaign spans) over cumulative rule output. Each source is plotted independently from zero, so neither line includes the other. Campaign dates are year-granularity.
Code Repositories detection strategy DET0805
MITRE names one behaviour worth catching for this technique and breaks it into 1 analytic, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Detection of Code Repositories
AN1937 · PRE
Much of this activity may have a very high occurrence and associated false positive rate, as well as potentially taking place outside the visibility of the target organization, making detection difficult for defenders. Detection efforts may be focused on related stages of the adversary lifecycle, such as during Initial Access.
Application developers uploading to public code repositories should be careful to avoid publishing sensitive information such as credentials and API keys.
Scan public code repositories for exposed credentials or other sensitive information before making commits. Ensure that any leaked credentials are removed from the commit history, not just the current latest version of the code.