Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
GitBackdorizer — GitBackdorizer (bad name, I know!) Is a proof of concept from Ulisses Castro's talk - 50 ton of backdoors (https://www.slideshare.net/ulissescastro/50-ton-of-backdoors) that uses the lack of user attention to steal git access credentials. | Kitploit
Tools/GitHubGitHub/unkl4b/gitbackdorizer
Penetration TestingSocial EngineeringRed TeamingPayload Development
GitHubunkl4b/gitbackdorizer

GitBackdorizer

GitBackdorizer (bad name, I know!) Is a proof of concept from Ulisses Castro's talk - 50 ton of backdoors (https://www.slideshare.net/ulissescastro/50-ton-of-backdoors) that uses the lack of user attention to steal git access credentials.

View Repository
51108 years agoReviewed by Kitploit

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

GitBackdorizer (BETA)

GitBackdorizer is a proof of concept, fully inspired in Ulisses Castro's 50 ton of backdoors talk, that abuses the lack of user attention to steal git access credentials.

How it Works

GitBackdorizer consists of three pieces: handler, dropper and the payload.

Handler

The handler sets up a HTTP server to capture the credentials and offers a menu to configure the dropper's payload. The dropper delivery is responsability of the attacker.

Dropper

The dropper is designed to have the highest possible compatibility, avoiding any non-sh specific feature. It works by:

  • Identify if the backdorized git hook is the pre-push hook or any other
  • Drop the backdoor payload to the specific hook
  • Give execution permission

Payload

Payloads are also designed to have the highest possible compatibility avoiding non-sh features.There are currently two types of payload, the generic and the pre-push specific.

The generic payload tries to identify the remote type (HTTPS/SSH) by:

  • Checking the current branch: git branch --contains HEAD
  • Collecting the remote name of the branch (through git config)
  • Collecting the remote url of the remote name (through git config) Then it will check if url is https or ssh.

The pre-push payload will check directly the provided git information for the url (second hook parameter for pre-push).

Demo

How to use gitbackdorizer to exploit user confidence and steal their credentials:

GitBackdorizer - stealing credentials

Greetz

  • Ulisses Castro - 50 ton of backdoors (https://www.slideshare.net/ulissescastro/50-ton-of-backdoors)
  • Giovani Silva - Wrote Infection Shell Script
Download Tool