A recruiter ZIP hid a Git filter that could execute during git status
Repository internals can carry executable local settings alongside apparently ordinary job documents.

A reported job offer came with a ZIP containing documents, source code, and a complete .git directory. That last inclusion carried the trap: local Git settings could tell the recipient’s tools to execute a program while examining the project.
The researcher describes a clean filter assigned to matching files and a post-checkout hook that called git status. Git can apply a clean filter while comparing working-tree content with its stored representation. The report says a harmless test filter confirmed that invocation.
This is conditional behavior. Merely downloading or extracting the archive is not the execution event described. File state and the Git operation matter, as do the tools that may invoke Git on your behalf. It would be wrong to turn the account into a claim that every status check runs every hook.
The distinction between a cloned repository and an archived .git directory is central. The archive carried local configuration that an ordinary clone of tracked project files would not inherit in the same way. It arrived with the machinery already pointed at a supplied executable.
Git’s own attributes documentation explains clean filters as content-conversion programs. That is a legitimate extension point. Here, the reported setup used the extension point to turn an inspection task into a possible execution task.
Source code has acquired a very demanding definition of paperwork.
For a hiring workflow, the practical boundary is earlier than running the build. You need a way to inspect an unfamiliar archive’s contents without asking development tools to initialize the supplied repository context. A file viewer and a trusted editor’s project mode can have very different behavior, even when both appear to be opening text.
An isolated environment is useful only if it is actually isolated from the things you care about. Mounting your usual home directory and passing through account credentials would undermine the reason for creating a separate space. Establish what the inspection environment can reach before opening the project inside it.
For a recruiter, distributing source through an established hosting service also gives the candidate a clearer starting point. An interview exercise should not require accepting an anonymous bundle of repository internals just to discover what the role involves.
The report is one person’s account, not proof that a named company knowingly operated a campaign or that any recipient was compromised. The observed configuration and the documented Git feature support a narrower conclusion: local repository settings deserve the same suspicion as the executable files they can launch.
If you received a similar bundle, preserve it for a qualified security reviewer rather than testing its scripts on your everyday machine. The interesting question is what your tools will do with the package. The contract can wait.