Farm repos and accounts, off GitHub.

• Repos and gists with signup automation that names your product, endpoints or signup flow
• Forks and copies that keep a toolkit alive after the original is removed
• Successor accounts that republish the same repos
• Pools of accounts used to farm your sign-in-with-GitHub route

GitHub reviews abuse reports against its own policies, so each report shows what the repo does, which service it targets and the evidence behind it: the repo, its commits and an archived copy.

Farm toolkits rarely copy your code, so a DMCA notice usually doesn't apply. The report is about abuse, not copyright, and it goes out from your domain so GitHub hears from the company being farmed.

We reported the operator's repos and accounts on 21 October. GitHub removed the first account on 23 October, two days later. The same day, 26 of its repos reappeared on the operator's own git server.

A successor account published about 15 farm repos between 25 and 28 October and was gone by the 28th. A third account was still live on 2 November, reported and checked daily. Read the full case.

Removing an account doesn't remove the toolkit. We check daily for forks, mirrors and successor accounts, report each one under the same case, and follow the operator to wherever the code moves next.

• Gitea and Forgejo servers
• Telegram takedowns
• Domain and mail takedowns
• Farm toolkit takedowns
• Free credit farming