---
title: "Discussion on \"A job offer on LinkedIn came with malware in a Git hook. It’s the “Contagious Interview” playbook\" | Hashnode"
description: "Discussion on \"A job offer on LinkedIn came with malware in a Git hook. It’s the “Contagious Interview” playbook\". A recruiter’s documentation pack hid a hook that runs a script on checkout. What it does, the campaign it matches, and how to check what you’re sent"
url: "https://hashnode.com/posts/contagious-interview-git-hook/6af1c5bb5e1a921f8e243de7"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [A job offer on LinkedIn came with malware in a Git hook. It’s the “Contagious Interview” playbook](https://itshuzaifa.hashnode.dev/contagious-interview-git-hook?utm_source=hashnode&utm_medium=feed)

A recruiter’s documentation pack hid a hook that runs a script on checkout. What it does, the campaign it matches, and how to check what you’re sent

Nov 9 · 10 min read · itshuzaifa.hashnode.dev  
Read the article

-   [#security](https://hashnode.com/tag/security)
-   [#cybersecurity](https://hashnode.com/tag/cybersecurity)
-   [#git](https://hashnode.com/tag/git)
-   [#malware](https://hashnode.com/tag/malware)
-   [#career](https://hashnode.com/tag/career)

## Written by

[Huzaifa Khan](https://hashnode.com/@huzaifa207)

@huzaifa207 · Lahore, Pakistan

  
[View profile](https://hashnode.com/@huzaifa207)

Full-stack engineer building web and desktop apps, AI backends, and secure cloud

I build products end to end: desktop apps in Rust and Tauri, real-time backends in Node.js, and AWS infrastructure defined in Terraform. I write about what I learn shipping them, from shrinking desktop apps to locking down cloud access. More at itshuzaifa.com.

## Responses 2

Markdown supported · ⌘↵ to post

[Linkjob AI](https://hashnode.com/@linkjob)

[Nov 9](https://hashnode.com/posts/contagious-interview-git-hook/6af1c5bb5e1a921f8e243de7/comment/6af210919c80d9d1b498c249)

The detail that the hook hides inside a recruiter's "documentation pack" and fires on checkout is what makes this so nasty, since people expect to clone a take-home before reading it. Treating any repo from an unknown recruiter as untrusted and opening it in a throwaway VM, or at least inspecting .git/hooks first, seems like a cheap habit worth adopting.

[Huzaifa Khan](https://hashnode.com/@huzaifa207)

[Nov 9](https://hashnode.com/posts/contagious-interview-git-hook/6af1c5bb5e1a921f8e243de7/comment/6af210919c80d9d1b498c249#reply-6af21e06bd19fc838ddec123)

Thanks, that’s the habit I hope people take away.

One twist: git clone never copies hooks, so a zip is how they plant one. A clone isn’t safe either. Campaigns like PolinRider hide code in ordinary config files, and it runs the moment you start the project. Hooks are only one of the risks. core.hooksPath, editor tasks that run when a folder opens, and install scripts can all run code, sometimes on a branch you haven’t opened yet.

I built LookFirst to check all of that without extracting or running anything. It recognises PolinRider by name, and it works on a cloned folder as well as a zip. It’s free, if you want to try it on your next take-home: [github.com/huzaifa207/lookfirst/releases/latest](https://github.com/huzaifa207/lookfirst/releases/latest)
