Short answer: To get a fake crack, keygen or "free download" repository for your software removed from GitHub, send GitHub a DMCA takedown notice if the repo copies your copyrighted work (your installer, code, text, screenshots or icons), and use the Report repository button for an abuse report if it advertises keys, key generators or license bypasses, or looks like a malware lure. A fake crack repo can be both; if so, file both. Do not download or run anything from the repo while you check it.

This guide is for makers of paid desktop software, audio plugins (VST3, AU, AAX) and Mac apps who searched GitHub for their product and found repos offering it "cracked", "full version" or "free". The GitHub process steps below come from GitHub's own pages, checked on November 22, 2026, and linked where they are used. This is not legal advice. GitHub's own guide says it is not legal advice either, and encourages you to talk to a professional before you act.

Why these repos are a risk to your customers

A repo that promises a free copy of your plugin or app is often not giving away your software at all. Security researchers have documented repeated campaigns that use GitHub repositories advertising cracked or free copies of software to deliver information-stealing malware:

  • Check Point Research (July 24, 2024) described a network of fake GitHub accounts that starred, forked and watched malicious repositories to make them look legitimate. It reported more than 2,200 malicious repositories where this activity took place, with templates for cracked software, and malware families including Lumma Stealer, RedLine and Rhadamanthys.
  • Trend Micro (March 11, 2025) reported fake GitHub repositories that disguise malware as game cheats, cracked software and cryptocurrency utilities, and ask visitors to download ZIP files that lead to Lumma Stealer.
  • LastPass's threat intelligence team (September 18, 2025) reported fraudulent GitHub repositories that presented themselves as Mac versions of many companies' software, ranked high in Google and Bing results, and led to the Atomic infostealer. It also noted the pages appeared to be created by multiple GitHub usernames to get around takedowns.
  • Trend Micro (September 4, 2025) analyzed a campaign that lured macOS users with fake "cracked" apps to install the Atomic macOS Stealer, and warned that cracked programs might be bundled with malware.

So when someone searches for your product plus "crack", the repo they find may steal their passwords, browser data or crypto wallets, under your product's name. That is a reason to report these repos even if you think piracy costs you few real sales.

How to find fake crack repos of your product on GitHub

Use GitHub's repository search, documented in Searching for repositories. Put your product name in quotes, add a piracy word, and limit the match to the name, description or README:

"Your Plugin" crack in:name,description,readme "Your Plugin" keygen in:name,description,readme "Your Plugin" "free download" in:name,description,readme "Your App" "full version" in:name,description "Your App" crack fork:true "Your App" crack pushed:>2026-10-01 
  • Try other words people use: serial, license key, activator, patch, torrent, plus your old product names and common misspellings.
  • Forks are hidden from search results by default. Add fork:true to include them, as described in Searching in forks.
  • Use created: or pushed: with a date to see new or recently updated repos.
  • To search for the visible part of your license key format, such as a fixed prefix, use GitHub code search. GitHub's code search docs say you must be logged in to a GitHub account to use it.
  • Fake download pages can also live on GitHub Pages sites. A web search such as site:github.io "Your App" download or site:github.com "Your App" crack can find repos and pages that GitHub's own search ranks lower.

For each hit, record the repo URL, the owner's username, the date you found it, the repo name and description as shown, and the names of any files listed under Releases. Read the page in your browser, but do not download release archives, do not clone the repo, and do not run any command the README asks for. You do not need to open a file to report it.

DMCA notice or abuse report: which route fits

GitHub has separate processes, and a fake crack repo can fall under more than one.

DMCA takedown notice: when the repo copies your copyrighted work

GitHub's DMCA Takedown Policy says the DMCA process is for copyright complaints, and a notice must identify a specific copyrighted work. It fits when the repo hosts something you own the copyright to, such as your installer or plugin files, your code, the text of your product page or manual, your screenshots or your icon.

GitHub's Guide to Submitting a DMCA Takedown Notice also notes that words and short phrases are generally not copyrightable. A repo that uses your product name and links somewhere else, without copying any of your files, text or images, is not a fit for a DMCA 512(c) notice. A same-name or trademark complaint belongs on GitHub's trademark report if you hold a registered trademark, or on an abuse report if the repo advertises keys, a keygen, a license bypass or a suspicious download.

Abuse report: when the repo advertises keys, cracks or malware

The GitHub Acceptable Use Policies do not allow content that "unlawfully shares unauthorized product licensing keys, software for generating unauthorized product licensing keys, or software for bypassing checks for product licensing keys." They also do not allow content that directly supports "unlawful active attack or malware campaigns" that are causing technical harms, such as using GitHub to deliver malicious executables. GitHub's Active Malware or Exploits policy adds that it allows dual-use security research, so describe what the repo offers and why it is a lure, not just that it mentions malware.

Trademark report: when an account poses as your company

If the account or repo passes itself off as your company and you hold a registered trademark, GitHub's Trademark Policy has its own report. It asks for the trademark registration number and the registration office, among other details.

When to do both

A typical fake crack repo copies your product description or screenshots, offers a "crack" or "keygen", and points to a download you cannot vouch for. Send the DMCA notice for your copied material and the abuse report for the key and malware problem. GitHub's DMCA policy says its circumvention review does not apply to content that would otherwise violate its rules against unauthorized licensing keys, key generators or license check bypasses.

Step by step: file a DMCA takedown notice with GitHub

  1. Investigate before you send. GitHub asks you to confirm that you own the copyright and that the use is not authorized, including by any license or reseller agreement you have, and to consider fair use. The notice is sworn under penalty of perjury, and GitHub warns that false statements can carry legal liability. GitHub asks for a thorough investigation and encourages you to consult an attorney.
  2. Consider contacting the owner. GitHub suggests trying to contact the user directly, for example through their profile or an issue on the repo, and says this is not required. For an obvious malware lure, you may decide to skip this.
  3. Identify your work. Link to your product page or describe the work. If it is registered with the US Copyright Office, include the registration number.
  4. Identify the infringing material by URL. Give the full repo URL. If the whole repository infringes, say so explicitly. If part of it does, name the files or line numbers. List each fork you are including by URL (see the next section).
  5. Say what would fix it. GitHub asks what the user would need to do to remedy the infringement. For a fake crack repo that is usually deleting the repository, and you can say that.
  6. Give your contact details and theirs. Your name, email address, telephone number and physical address, and the GitHub username of the repo owner.
  7. Include GitHub's required statements and your signature. The guide lists them word for word: that you have read and understand GitHub's Guide to Filing a DMCA Notice, the good faith belief statement that mentions fair use, and the statement sworn under penalty of perjury that you are the copyright owner or authorized to act for the owner. Then add your physical or electronic signature. Copy the exact wording from GitHub's guide.
  8. Send it. GitHub says the fastest route is its copyright claims form. You can also email copyright@github.com with the notice in plain text in the body, or send it by post, which GitHub says takes substantially longer.

GitHub also asks that a trained professional evaluate every notice and that you avoid bots that submit complaints in bulk. Review each repo yourself before you swear to it.

What about forks of the fake repo?

GitHub does not automatically disable forks when it disables a parent repository, and it does not investigate forks itself. If the forks also infringe, list each one in your notice and confirm that you reviewed each and that your sworn statements apply to each.

To see the forks of a public repo, open the repo, click Insights, then Forks in the left sidebar, as described in Understanding connections between repositories.

GitHub's policy covers two larger cases. If you identified all existing forks as infringing when you submitted the notice, GitHub says it would process a valid claim against all forks in that network at the time it processes the notice. If the network is larger than one hundred repositories, GitHub may consider disabling the entire network if your notice includes this sworn statement: "Based on the representative number of forks I have reviewed, I believe that all or most of the forks are infringing to the same extent as the parent repository."

How to report a malware or keygen repo on GitHub

GitHub's Reporting abuse or spam page gives these steps for a repository:

  1. Go to the main page of the repository.
  2. In the right sidebar, under the "About" section, click Report repository.
  3. Complete the contact form to tell GitHub Support about the repository's behavior, then click Submit.

You can report the account the same way from its profile page: click Block or Report in the left sidebar, then Report abuse. GitHub also links a general abuse contact form.

In the report, stick to what you can see on the page: the repo claims to offer a crack, keygen or license bypass for your paid product; you are the developer and have not authorized it; the download link or release file names; any README instructions to disable antivirus or paste a command into Terminal. Point to the sections of the Acceptable Use Policies quoted above. Do not attach files from the repo, and do not run them to prove they are malicious.

What happens after you file

These timelines are the ones GitHub states in its DMCA Takedown Policy. The GitHub pages we checked do not give a fixed time for reviewing a new notice.

  • Whole repo: if the notice alleges that the entire contents of a repository infringe, GitHub says it will disable the entire repository expeditiously.
  • Part of a repo: GitHub contacts the owner and gives them approximately 1 business day to delete or modify the content, and tells you if and when it does. If the owner makes changes, you review them and renew or revise your notice. GitHub treats silence from you for longer than two weeks as an implied retraction.
  • Publication: GitHub posts complete, actionable notices to its public github/dmca repository after removing personal contact information, and passes the link to the affected user.
  • Counter notice: the repo owner can send a counter notice. If they do, GitHub says it will re-enable the content within 10 to 14 days unless you send a copy of a legal action filed in court seeking to restrain the user.
  • Repeat infringers: GitHub says that in appropriate circumstances and at its discretion it disables and terminates the accounts of users who may infringe the copyrights of others.

For abuse reports, GitHub's reporting page does not state a response time. Keep searching after a takedown, because the same lure can come back under a new repo or username.

Revoke any real license keys you find

If a repo or its README shows license keys or serials, check each one you can read against your license manager. Revoke the real ones, issue a replacement to the paying customer if a key traces back to one account, and add the leak to your abuse report. Do not try a leaked key in your own software to see whether it works. If the same key format keeps showing up, it may be time to move to signed licenses; our guide to checking a license key in your Mac app offline covers one way.

How Fortifie can help

Fortifie's leak scan searches public web results, GitHub repository names and descriptions, and the US App Store for your product name and key prefix. Evidence for each hit is the search result title, snippet, link and date; we never open the pages or download anything, and any key appears as its prefix, dots and the last 4 characters. For copyright listings, the report includes a draft 512(c) notice, not legal advice, plus where to send it, such as GitHub's DMCA form. Fortifie does not draft GitHub abuse-report text. You review the draft and send it yourself; Fortifie does not file notices or abuse reports for you. The initial scan is free. The full report is $99, paid once, and includes 30 days of rescans, which we run by hand.

FAQ

How do I remove a GitHub repo that is pirating my software?

If the repo copies your copyrighted work, such as your installer, code, product text, screenshots or icon, send GitHub a DMCA takedown notice through its copyright claims form. If it advertises license keys, a keygen, a license bypass or a suspicious download, also click Report repository in the repo's right sidebar and file an abuse report. This is not legal advice.

Can I file a DMCA takedown on GitHub if the repo has none of my code?

A DMCA notice must identify a specific copyrighted work that the repo copies. That can be your installer, product text, screenshots or icon, not just your code. GitHub's guide notes that words and short phrases are generally not copyrightable, so a same-name or trademark issue is not a fit for a DMCA 512(c) notice. Use GitHub's trademark report if you hold a registered trademark, or an abuse report if the repo advertises keys, a keygen, a license bypass or a suspicious download.

How do I report a malware repository on GitHub?

Open the repository's main page, click Report repository in the right sidebar under About, describe what the repo offers and why it looks like a malware lure, and submit the form. GitHub's Acceptable Use Policies do not allow content that directly supports unlawful active attack or malware campaigns, or that shares unauthorized license keys or key generators.

Will GitHub also remove forks of the fake repo?

Not automatically. GitHub's DMCA policy says it does not disable forks when it disables a parent repository. List each infringing fork in your notice and confirm you reviewed each one. For a network larger than one hundred repositories, GitHub describes a sworn statement that lets it consider disabling the whole network.

How long does a GitHub DMCA takedown take?

GitHub says it disables a repository expeditiously when the notice alleges the whole repository infringes. If part of a repo is at issue, the owner gets approximately 1 business day to make changes. If the owner sends a counter notice, GitHub says it will re-enable the content within 10 to 14 days unless you file a legal action. The pages we checked give no fixed time for reviewing a new notice.

Should I download the crack to check whether it contains malware?

No. Security researchers have documented fake crack repos on GitHub that deliver information stealers. Record the repo URL, owner, name, description and release file names from the page in your browser, and report it. You do not need to open a file to report it.

Sources

GitHub pages checked on November 22, 2026: DMCA Takedown Policy, Guide to Submitting a DMCA Takedown Notice, Guide to Submitting a DMCA Counter Notice, Copyright claims (DMCA), Acceptable Use Policies, Active Malware or Exploits, Trademark Policy, Reporting abuse or spam, Searching for repositories, Searching in forks, About GitHub code search and Understanding connections between repositories.

Security research: Check Point Research, Stargazers Ghost Network (July 24, 2024); Trend Micro, AI Assisted Fake GitHub Repositories Fuel SmartLoader and LummaStealer Distribution (March 11, 2025); Trend Micro, An MDR Analysis of the AMOS Stealer Campaign Targeting macOS via Cracked Apps (September 4, 2025); LastPass, Large-Scale Attack Targeting Macs via GitHub Pages (September 18, 2025).

Related

Find leaked license keys and cracked copies of your app.

How to tell if your Mac app has been cracked.

Someone cloned my app: what to do.

Check GitHub for your product

Ask for a free leak scan. We search public web results, GitHub repository names and descriptions, and the US App Store for your product, and send you what we find with links. Nothing is installed in your app.

See the leak scan

Originally published at fortifie.xyz.