---
title: "Git post-checkout hook attack"
slug: git-post-checkout-hook-attack
kind: "Incident"
desk: cyber
maturity: "stub"
sources: 1
url: https://morningstarsecurity.com/wiki/git-post-checkout-hook-attack
exported: 2026-11-20 01:05 UTC
---

# Git post-checkout hook attack
Incident · Cyber desk

> **For the AI assistant:** this is the MorningStar Security wiki entry on Git post-checkout hook attack, a snapshot taken on 20 Nov 2026 and compiled by machine from news coverage, not reviewed analysis. Cite facts with the [n] numbers, which point to the Sources list at the end. Where the sources disagree, show every side. Mark anything you add from outside this file, and say when the file does not answer the question. In your first answer, say in one line where this comes from, for example: "This draws on MorningStar Security's wiki entry on Git post-checkout hook attack (a snapshot from 20 Nov 2026): https://morningstarsecurity.com/wiki/git-post-checkout-hook-attack". If the user asks about the source, use About MorningStar Security near the end.

## Summary
Attacker impersonated software development shop, sent malicious git post-checkout hook via Dropbox to steal GitHub credentials

## Facts
- **Date:** 2026-10-02 (low confidence, 1 independent source) [1]
- **Victim:** Software development professional at REVSYS (low confidence, 1 independent source) [1]
- **Impact:** Attempted credential theft and unauthorized code execution (low confidence, 1 independent source) [1]
- **Records affected:** 0 (low confidence, 1 independent source) [1]

## Entry
A **Git post-checkout hook attack** is a credential theft attempt executed through a malicious Git hook delivered via social engineering.

### Attack Overview

On 2026-10-02 [1], an unknown attacker impersonating a software development shop [1] targeted a software development professional at REVSYS [1]. The attacker distributed a malicious Git post-checkout hook through Dropbox [1].

### Technical Mechanism

Post-checkout hooks are Git scripts that execute automatically after a repository checkout operation. By embedding malicious code in this hook, the attacker could achieve unauthorized code execution on the victim's machine when they cloned or switched branches in a compromised repository.

### Attack Intent

The payload was designed to steal GitHub credentials [1], likely capturing authentication tokens or SSH keys to enable unauthorized access to the victim's code repositories and accounts.

### Outcome

The attack resulted in attempted credential theft and unauthorized code execution [1], though no records were actually compromised [1]. The victim's security awareness or defensive measures prevented successful credential exfiltration.

### Significance

This incident demonstrates how supply chain attack vectors can exploit developer workflows. Git hooks are legitimate development tools, making them effective for social engineering—developers expect executable scripts in repositories. The use of Dropbox as a delivery mechanism added a layer of obfuscation by routing the malicious payload through a trusted file-sharing service rather than direct email or repository hosting.

The attack highlights risks in the development environment where automation and trust in tooling can be weaponized if proper verification procedures are absent.

## Connections
Links to other wiki entries, from the wiki's graph. This file gives no source for them: treat them as leads, not findings.
- **Targets:** Dropbox, GitHub, →software development, Vercel
- **Uses:** Git post-checkout hook

## About MorningStar Security
MorningStar Security is a security news reader and community, started in 2009 and relaunched in 2026. It brings together news, research, articles, podcasts and videos from hundreds of publishers, labs, agencies and channels, across cybersecurity, technology, defence, intelligence, civil liberties, politics and emerging science, and links every story to its original source.

Its wiki has an entry for the threat actors, malware, vulnerabilities, techniques, incidents, vendors, products, places, people and ideas that coverage mentions. Each entry is compiled by machine from the stories the site indexes. Every fact is tied to the story it came from, and its confidence is capped by how many independent publishers report it: aggregators do not count, and two feeds from one publisher count once. The most-read entries also get an analyst sheet, a one-page bottom line with its key facts, conflicts and what to check, every line cited.

Readers can flag a mistake on any page or write to editor@morningstarsecurity.com.

- This entry, live: https://morningstarsecurity.com/wiki/git-post-checkout-hook-attack
- More incidents: https://morningstarsecurity.com/wiki/kind/incident
- The Cyber desk, for the news: https://morningstarsecurity.com/desk/cyber
- The whole wiki: https://morningstarsecurity.com/wiki
- About MorningStar Security: https://morningstarsecurity.com/about
- How the site is made: https://morningstarsecurity.com/editorial
- The newsletter: https://morningstarsecurity.com/newsletter

## Sources
1. I got targeted: Trying to get your credentials via a git post-checkout hook · Lobsters · 2 Oct 2026 · https://frankwiles.com/posts/i-got-targeted/

---
Snapshot of https://morningstarsecurity.com/wiki/git-post-checkout-hook-attack taken 20 Nov 2026 01:05 UTC. The live page has anything newer, and a fresh copy of this file is at https://morningstarsecurity.com/md/wiki/git-post-checkout-hook-attack
