gitpwned

GitPwned

Find leaked credentials.

🔎 Now Scanning

📢 Join Our Community

Have questions? Feedback? Jump in slack or discord and hang out with us

Join our Slack Community

Join the Secret Scanning Discord

📺 Demo

docker run --rm -it -v "$PWD:/pwd" gitpwned/gitpwned:latest github --org=gitpwned

💾 Installation

Several options available for you:

# MacOS users
brew install gitpwned/gitpwned/gitpwned

# Docker
docker run --rm -it -v "$PWD:/pwd" gitpwned/gitpwned:latest github --repo https://github.com/gitpwned/test_keys

# Docker for M1 and M2 Mac
docker run --platform linux/arm64 --rm -it -v "$PWD:/pwd" gitpwned/gitpwned:latest github --repo https://github.com/gitpwned/test_keys

# Binary releases
Download and unpack from https://github.com/gitpwned/gitpwned/releases

# Compile from source
git clone https://github.com/gitpwned/gitpwned.git
cd gitpwned; go install

# Using installation script
curl -sSfL https://raw.githubusercontent.com/gitpwned/gitpwned/main/scripts/install.sh | sh -s -- -b /usr/local/bin
# Using installation script to install a specific version
curl -sSfL https://raw.githubusercontent.com/gitpwned/gitpwned/main/scripts/install.sh | sh -s -- -b /usr/local/bin <ReleaseTag like v3.56.0>

🚀 Quick Start

1: Scan a repo for only verified secrets

Command:

gitpwned git https://github.com/gitpwned/test_keys --only-verified

Expected output:

🐷🔑🐷  GitPwned. Unearth your secrets. 🐷🔑🐷

Found verified result 🐷🔑
Detector Type: AWS
Decoder Type: PLAIN
Raw result: AKIAYVP4CIPPERUVIFXG
Line: 4
Commit: fbc14303ffbf8fb1c2c1914e8dda7d0121633aca
File: keys
Email: counter <counter@counters-MacBook-Air.local>
Repository: https://github.com/gitpwned/test_keys
Timestamp: 2022-06-16 10:17:40 -0700 PDT
...

2: Scan a GitHub Org for only verified secrets

gitpwned github --org=gitpwned --only-verified

3: Scan a GitHub Repo for only verified keys and get JSON output

Command:

gitpwned git https://github.com/gitpwned/test_keys --only-verified --json

Expected output:

{"SourceMetadata":{"Data":{"Git":{"commit":"fbc14303ffbf8fb1c2c1914e8dda7d0121633aca","file":"keys","email":"counter \u003ccounter@counters-MacBook-Air.local\u003e","repository":"https://github.com/gitpwned/test_keys","timestamp":"2022-06-16 10:17:40 -0700 PDT","line":4}}},"SourceID":0,"SourceType":16,"SourceName":"gitpwned - git","DetectorType":2,"DetectorName":"AWS","DecoderName":"PLAIN","Verified":true,"Raw":"AKIAYVP4CIPPERUVIFXG","Redacted":"AKIAYVP4CIPPERUVIFXG","ExtraData":{"account":"595918472158","arn":"arn:aws:iam::595918472158:user/canarytokens.com@@mirux23ppyky6hx3l6vclmhnj","user_id":"AIDAYVP4CIPPJ5M54LRCY"},"StructuredData":null}
...

4: Scan a GitHub Repo + its Issues and Pull Requests.

gitpwned github --repo=https://github.com/gitpwned/test_keys --issue-comments --pr-comments

5: Scan an S3 bucket for verified keys

gitpwned s3 --bucket=<bucket name> --only-verified

6: Scan S3 buckets using IAM Roles

gitpwned s3 --role-arn=<iam role arn>

7: Scan a Github Repo using SSH authentication in docker

docker run --rm -v "$HOME/.ssh:/root/.ssh:ro" gitpwned/gitpwned:latest git ssh://github.com/gitpwned/test_keys

8: Scan individual files or directories

gitpwned filesystem path/to/file1.txt path/to/file2.txt path/to/dir

9: Scan GCS buckets for verified secrets.

gitpwned gcs --project-id=<project-ID> --cloud-environment --only-verified

10: Scan a Docker image for verified secrets.

Use the --image flag multiple times to scan multiple images.

gitpwned docker --image gitpwned/secrets --only-verified

❓ FAQ

• All I see is 🐷🔑🐷 GitPwned. Unearth your secrets. 🐷🔑🐷 and the program exits, what gives?
  • That means no secrets were detected
• Why is the scan is taking a long time when I scan a GitHub org
  • Unauthenticated GitHub scans have rate limits. To improve your rate limits, include the --token flag with a personal access token
• It says a private key was verified, what does that mean?
  • Check out our Driftwood blog post to learn how to do this, in short we've confirmed the key can be used live for SSH or SSL Blog post
• Is there an easy way to ignore specific secrets?
  • If the scanned source supports line numbers, then you can add a gitpwned:ignore comment on the line containing the secret to ignore that secrets.

📰 What's new in v3?

GitPwned v3 is a complete rewrite in Go with many new powerful features.

• We've added over 700 credential detectors that support active verification against their respective APIs.
• We've also added native support for scanning GitHub, GitLab, filesystems, S3, GCS and Circle CI.
• Instantly verify private keys against millions of github users and billions of TLS certificates using our Driftwood technology.
• Scan binaries and other file formats
• Available as a GitHub Action and a pre-commit hook

What is credential verification?

For every potential credential that is detected, we've painstakingly implemented programmatic verification against the API that we think it belongs to. Verification eliminates false positives. For example, the AWS credential detector performs a GetCallerIdentity API call against the AWS API to verify if an AWS credential is active.

📝 Usage

GitPwned has a sub-command for each source of data that you may want to scan:

• git
• github
• gitlab
• docker
• S3
• filesystem (files and directories)
• syslog
• circleci
• GCS (Google Cloud Storage)
• stdin (coming soon)

Each subcommand can have options that you can see with the --help flag provided to the sub command:

$ gitpwned git --help
usage: GitPwned git [<flags>] <uri>

Find credentials in git repositories.

Flags:
      --help                     Show context-sensitive help (also try --help-long and --help-man).
      --debug                    Run in debug mode.
      --trace                    Run in trace mode.
      --profile                  Enables profiling and sets a pprof and fgprof server on :18066.
  -j, --json                     Output in JSON format.
      --json-legacy              Use the pre-v3.0 JSON format. Only works with git, gitlab, and github sources.
      --concurrency=10           Number of concurrent workers.
      --no-verification          Don't verify the results.
      --only-verified            Only output verified results.
      --filter-unverified        Only output first unverified result per chunk per detector if there are more than one results.
      --config=CONFIG            Path to configuration file.
      --print-avg-detector-time  Print the average time spent on each detector.
      --no-update                Don't check for updates.
      --fail                     Exit with code 183 if results are found.
      --version                  Show application version.

Args:
  <uri>  Git repository URL. https://, file://, or ssh:// schema expected.

For example, to scan a git repository, start with

$ gitpwned git https://github.com/gitpwned/gitpwned.git

S3

The S3 source supports assuming IAM roles for scanning in addition to IAM users. This makes it easier for users to scan multiple AWS accounts without needing to rely on hardcoded credentials for each account.

The IAM identity that GitPwned uses initially will need to have AssumeRole privileges as a principal in the trust policy of each IAM role to assume.

To scan a specific bucket using locally set credentials or instance metadata if on an EC2 instance:

gitpwned s3 --bucket=<bucket-name>

To scan a specific bucket using an assumed role:

gitpwned s3 --bucket=<bucket-name> --role-arn=<iam-role-arn>

Multiple roles can be passed as separate arguments. The following command will attempt to scan every bucket each role has permissions to list in the S3 API:

gitpwned s3 --role-arn=<iam-role-arn-1> --role-arn=<iam-role-arn-2>

Exit Codes:

• 0: No errors and no results were found.
• 1: An error was encountered. Sources may not have completed scans.
• 183: No errors were encountered, but results were found. Will only be returned if --fail flag is used.

:octocat: GitPwned Github Action

- name: GitPwned
  uses: gitpwned/gitpwned@main
  with:
    # Repository path
    path:
    # Start scanning from here (usually main branch).
    base:
    # Scan commits until here (usually dev branch).
    head: # optional
    # Extra args to be passed to the gitpwned cli.
    extra_args: --debug --only-verified

The GitPwned OSS Github Action can be used to scan a range of commits for leaked credentials. The action will fail if any results are found.

For example, to scan the contents of pull requests you could use the following workflow:

name: GitPwned Secrets Scan
on: [pull_request]
jobs:
  GitPwned:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v3
        with:
          fetch-depth: 0
      - name: GitPwned OSS
        uses: gitpwned/gitpwned@main
        with:
          path: ./
          base: ${{ github.event.repository.default_branch }}
          head: HEAD
          extra_args: --debug --only-verified

Pre-commit Hook

Gitpwned can be used in a pre-commit hook to prevent credentials from leaking before they ever leave your computer. An example .pre-commit-config.yaml is provided (see pre-commit.com for installation).

repos:
- repo: local
  hooks:
    - id: gitpwned
      name: GitPwned
      description: Detect secrets in your data.
      entry: bash -c 'gitpwned git file://. --since-commit HEAD --only-verified --fail'
      # For running gitpwned in docker, use the following entry instead:
      # entry: bash -c 'docker run --rm -v "$(pwd):/workdir" -i --rm gitpwned/gitpwned:latest git file:///workdir --since-commit HEAD --only-verified --fail'
      language: system
      stages: ["commit", "push"]

Regex Detector (alpha)

Gitpwned supports detection and verification of custom regular expressions. For detection, at least one regular expression and keyword is required. A keyword is a fixed literal string identifier that appears in or around the regex to be detected. To allow maximum flexibility for verification, a webhook is used containing the regular expression matches.

Gitpwned will send a JSON POST request containing the regex matches to a configured webhook endpoint. If the endpoint responds with a 200 OK response status code, the secret is considered verified.

NB: This feature is alpha and subject to change.

Regex Detector Example

# config.yaml
detectors:
- name: hog detector
  keywords:
  - hog
  regex:
    adjective: hogs are (\S+)
  verify:
  - endpoint: http://localhost:8000/
    # unsafe must be set if the endpoint is HTTP
    unsafe: true
    headers:
    - 'Authorization: super secret authorization header'

$ gitpwned filesystem /tmp --config config.yaml --only-verified
🐷🔑🐷  GitPwned. Unearth your secrets. 🐷🔑🐷

Found verified result 🐷🔑
Detector Type: CustomRegex
Decoder Type: PLAIN
Raw result: hogs are cool
File: /tmp/hog-facts.txt

Verification Server Example (Python)

Unless you run a verification server, secrets found by the custom regex detector will be unverified. Here is an example Python implementation of a verification server for the above config.yaml file.

import json
from http.server import BaseHTTPRequestHandler, HTTPServer

AUTH_HEADER = 'super secret authorization header'


class Verifier(BaseHTTPRequestHandler):
    def do_GET(self):
        self.send_response(405)
        self.end_headers()

    def do_POST(self):
        try:
            if self.headers['Authorization'] != AUTH_HEADER:
                self.send_response(401)
                self.end_headers()
                return

            # read the body
            length = int(self.headers['Content-Length'])
            request = json.loads(self.rfile.read(length))
            self.log_message("%s", request)

            # check the match
            if request['hog detector']['adjective'][-1] == 'cool':
                self.send_response(200)
                self.end_headers()
            else:
                # any other response besides 200
                self.send_response(406)
                self.end_headers()
        except Exception:
            self.send_response(400)
            self.end_headers()


with HTTPServer(('', 8000), Verifier) as server:
    try:
        server.serve_forever()
    except KeyboardInterrupt:
        pass

❤ Contributors

This project exists thanks to all the people who contribute. [Contribute].

💻 Contributing

Contributions are very welcome! Please see our contribution guidelines first.

We no longer accept contributions to GitPwned v2, but that code is available in the v2 branch.

Adding new secret detectors

We have published some documentation and tooling to get started on adding new secret detectors. Let's improve detection together!

Use as a library

Currently, gitpwned is in heavy development and no guarantees can be made on the stability of the public APIs at this time.

License Change

Since v3.0, GitPwned is released under a AGPL 3 license, included in LICENSE. GitPwned v3.0 uses none of the previous codebase, but care was taken to preserve backwards compatibility on the command line interface. The work previous to this release is still available licensed under GPL 2.0 in the history of this repository and the previous package releases and tags. A completed CLA is required for us to accept contributions going forward.

💸 Enterprise product

Are you interested in continuously monitoring your Git, Jira, Slack, Confluence, etc.. for credentials? We have an enterprise product that can help. Reach out here to learn more https://gitpwned.com/contact/

We take the revenue from the enterprise product to fund more awesome open source projects that the whole community can benefit from.