Skip to content

Commit ecfb2e2

Browse files
committed
Added information on how to identify tampered commit dates, and sample use-cases to the index
1 parent 82698b0 commit ecfb2e2

File tree

2 files changed

+21
-0
lines changed

2 files changed

+21
-0
lines changed

docs/awesome_features.md

+14
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,20 @@ gitxray -r https://github.com/SampleOrg/SampleRepo -v -f user_input
3535

3636
Associations MUST NOT be directly and blindly used to report fake or shadow accounts. They are automatic observations from a piece of well-intended code. Do NOT treat association results as findings directly. We must protect open-source projects by first and foremost respecting open-source developers. Ensure that any actions taken are thoughtful and based on solid evidence, not just automated associations.
3737

38+
## Untrustworthy Repositories and Activity 🏴
39+
40+
`gitxray` can be used to protect yourself, your team and your customers from fake Repositories and suspicious activity. For example, by analyzing commit dates and comparing them to the account creation timestamp of contributors, `gitxray` can flag inconsistencies that may indicate:
41+
42+
* Tampered Commits: Some repositories may be manipulated to appear older than they actually are, such as claiming that all commits date back six years when the repository was only created a week ago. This tactic is often used to increase perceived value. Unfortunately, altering commit dates is relatively easy in Git, and GitHub is no exception. More on this [here](https://www.reddit.com/r/git/comments/ympce5/is_it_possible_to_change_commit_date/).
43+
44+
* Reclaimed Usernames: Trusted contributors might have had their accounts deleted and then re-registered by malicious actors. GitHub allows a username to be re-released after 90 days, making this a possible attack vector. Learn more about GitHub’s account deletion policy [here](https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/deleting-your-personal-account#deleting-your-personal-account).
45+
46+
Although we always recommend running a full unfiltered verbose X-Ray, it is possible to focus on unreliable historic activity by filtering for Warning keywords:
47+
48+
```
49+
gitxray -o https://github.com/SampleOrg -v -f warning
50+
```
51+
3852
## The PR Rejection Awards 🏆
3953

4054
Another `gitxray` feature is the ability to list a TOP 3 of GitHub accounts that have tried to submit Pull Requests to the repository, which ended up closed AND NOT merged. In certain emotional scenarios, this could be paraphrased as _rejected PRs_. Kidding aside, in some cases, this could lead to identifying Contributors who have repeatedly failed at merging a very evidently unaligned piece of code to a branch (I know, it sounds unlikely for an account to try and merge backdoor.py repeatedly... but is it?).

docs/index.md

+7
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,13 @@ The Octocat getting X-Rayed | [![Build Workflows](https://github.com/kulkansecu
66
![Gitxray Logo](https://kulkansecurity.github.io/gitxray/images/logo_gitxray.png "Gitxray Logo") | ![Gitxray Console](https://kulkansecurity.github.io/gitxray/images/console_gitxray.png "Gitxray Console")
77
<div style="clear: both;"></div>
88

9+
# What is it for?
10+
* [Finding sensitive information in contributor profiles](/awesome_features/#unintended-disclosures-in-contributor-profiles) disclosed by accident within, for example, Armored PGP Keys, or Key Names.
11+
* Identifying threat actors in a Repository. [You may spot co-owned or shared accounts](/awesome_features/#spotting-shared-co-owned-or-fake-contributors), as well as inspect public events to [spot fake Stargazers](/awesome_features/#fake-stars-private-repos-gone-public-and-more).
12+
* Collecting [email addresses and analyzing contributor accounts](/more_features/#lots-of-e-mail-addresses-and-profiling-data) belonging to GitHub organizations and repositories.
13+
* Identifying fake or infected Repositories. It can [detect tampered commit dates](/awesome_features/#untrustworthy-repositories-and-activity) as well as, for example, [Release assets updated post-release](/more_features/#looking-out-for-malicious-releases-and-assets).
14+
* And so. much. more.
15+
916
# Getting started
1017
* [Installing Gitxray](installing.md)
1118
* [Awesome Features](awesome_features.md) &#128171;

0 commit comments

Comments
 (0)