PhishPin / Brands Live Phishing Data / Tech, email & cloud / GitHub
GitHub phishing: sites, fake domains & scam patterns
PhishPin's phishing-feed index currently lists 14 hostnames that reference GitHub, across 18 reported URLs from 1 of 5 threat feeds we track. GitHub ranks #181 of 579 brands we track by reported hosts. In the last 15 days, 11 newly registered domains contained or closely resembled the name.
Tech, email & cloud · rank #181 of 579 by reported hosts
Key findings for GitHub
- Impersonation pressure is Elevated (35/100): GitHub has more reported hosts than 68% of the 579 brands we track.
- That is 0.1× the average for tech, email & cloud (144 hosts per brand).
- 9 hosts (64%) hide the GitHub name in a subdomain of an unrelated site, the trick that makes a link look official at a glance.
- The most common ending is .dev (4 hosts, 29%).
- 11 lookalike domains were registered in the last 15 days, 4 of them in the three most recent days of data.
- 5 of the new domains are typo or look-alike-character copies, which are the hardest for people to spot.
How attackers fake GitHub
These breakdowns cover all 14 matching hostnames, not only the rows listed below.
Top endings (TLDs)
Hostname tricks
Hosts reported in phishing feeds
The most widely reported hostnames that reference GitHub, ranked by how many feeds list them and then by reported URLs. Search, filter and export all 14 rows.
| # | Hostname (defanged) | Pattern | Feeds | URLs |
|---|---|---|---|---|
| 1 | thenofogithubserver[.]ga | name in domain | 1 feed | 3 |
| 2 | thegarderhubservergithubweb[.]ml | name in domain | 1 feed | 2 |
| 3 | thesmallestgithubcoder[.]ga | name in domain | 1 feed | 2 |
| 4 | github[.]090227[.]xyz | subdomain trick | 1 feed | 1 |
| 5 | github[.]ddxm[.]pp[.]ua | subdomain trick | 1 feed | 1 |
| 6 | githubsol[.]pages[.]dev | subdomain trick | 1 feed | 1 |
| 7 | kvideok-github-io-sll2[.]vercel[.]app | subdomain trick | 1 feed | 1 |
| 8 | newworkergithub[.]aalireza1371[.]workers[.]dev | subdomain trick | 1 feed | 1 |
| 9 | pro-trezor-github[.]webflow[.]io | subdomain trick | 1 feed | 1 |
| 10 | steamavatar[.]githubspeed[.]workers[.]dev | subdomain trick | 1 feed | 1 |
| 11 | theynotbedonebygithub[.]ga | name in domain | 1 feed | 1 |
| 12 | tryinggithubs[.]ga | name in domain | 1 feed | 1 |
| 13 | web-start-doc-trezor-github-io[.]pages[.]dev | subdomain trick | 1 feed | 1 |
| 14 | wechats-app-github-l281yfkd1-wechats-app[.]vercel[.]app | subdomain trick | 1 feed | 1 |
Is your brand in these feeds?
Free check: email-spoofing gaps, registered lookalikes and feed listings for your own domain. About a minute, public DNS only.
New lookalike domains registered recently
Domains registered in the last 15 days that contain GitHub's name, sit one character away from it or use look-alike characters. Attackers often register these days before sending the first email.
Registrations per day
Top endings of new lookalikes
| # | Domain (defanged) | Why it matched | Registered |
|---|---|---|---|
| 1 | gifthub[.]space | 1 character off | 28 Oct 2026 · 4 days ago |
| 2 | gihhub[.]club | 1 character off | 25 Oct 2026 · 7 days ago |
| 3 | gifthub[.]co[.]il | 1 character off | 25 Oct 2026 · 7 days ago |
| 4 | gpthub[.]top | 1 character off | 20 Oct 2026 · 12 days ago |
| 5 | githubb[.]online | 1 character off | 17 Oct 2026 · 15 days ago |
| 6 | githubuncensoredai[.]com | contains brand name | 31 Oct 2026 · yesterday |
| 7 | uncensoredaigithub[.]com | contains brand name | 31 Oct 2026 · yesterday |
| 8 | cngithub[.]top | contains brand name | 29 Oct 2026 · 3 days ago |
| 9 | elmetgithub[.]courses | contains brand name | 29 Oct 2026 · 3 days ago |
| 10 | github-wenjian[.]cn | contains brand name | 28 Oct 2026 · 4 days ago |
| 11 | github-whatsapp[.]hl[.]cn | contains brand name | 25 Oct 2026 · 7 days ago |
How GitHub phishing works
Phishing against GitHub follows patterns common to tech, email & cloud. Typical lures:
- A "password expires today" or "mailbox full" email with a link to a fake sign-in page.
- A shared-document or e-signature request from a compromised contact that leads to a credential-harvesting page.
- A security alert about a login from an unfamiliar country that asks you to "secure your account".
- A billing or renewal notice with a phone number to call for a refund.
Red flags
- The sign-in page is on a domain you do not recognise, even if the logo and layout look perfect.
- A document or voicemail arrives from a colleague you were not expecting to hear from.
- The message pushes you to sign in immediately instead of going to the service yourself.
Real GitHub domains
If the address in your browser is not one of these (or a subdomain of them), it is not GitHub. The list is not exhaustive.
github.comgithub.iogithubusercontent.comIf you already clicked or entered details
Change the password from a clean device, sign out all sessions, review mailbox rules and connected apps for anything you did not create, and turn on multi-factor authentication. Tell your IT team, because stolen mailbox logins are often used to attack colleagues next.
Protecting a brand like GitHub from lookalike domains
If you run security, brand or fraud for a company that is copied this way, this is the order that works in practice:
- Enforce DMARC. Move your policy to quarantine, then reject, so attackers cannot send mail that passes as your domain.
- Watch new registrations. Lookalikes appear daily; the earlier you see one, the sooner you can act, ideally before the first email goes out.
- Register the obvious typos and keyword variants you can afford to hold, and check which lookalikes are already registered by someone else.
- Report fast. A live fake needs a request to the registrar and host, plus a report to browser safe-browsing lists and the public feeds shown above.
- Tell your customers where you will and will not ask for logins, codes or payments.
Protect your brand from lookalike domains
GitHub is one of 579 brands in this index, but attackers copy any company whose customers log in or pay. PhishPin checks your domain for registered lookalikes, email-spoofing gaps and listings in these same phishing feeds, then helps you get the fakes taken down.
Audits use public data only – we never touch your servers. Results within 24 hours.
Questions about GitHub phishing
How can I tell if a message from GitHub is phishing?
Check the sender and link domain first. The sign-in page is on a domain you do not recognise, even if the logo and layout look perfect. A document or voicemail arrives from a colleague you were not expecting to hear from. The message pushes you to sign in immediately instead of going to the service yourself. When in doubt, do not use the link: type github.com into your browser or open the official app.
How many GitHub phishing sites has PhishPin found?
As of 1 Nov 2026, 14 hostnames referencing GitHub appear in the phishing feeds PhishPin indexes (18 reported URLs). These are reported hostnames, not a count of sites that are online today; many are removed quickly and some matches are coincidental.
What do fake GitHub domains look like?
In our data, the most common ending for reported hosts is .dev. 9 hosts put the brand name in a subdomain of an unrelated site. Always read the part of the address just before the first single slash: that is the real site. Real GitHub addresses end in github.com.
What should I do if I entered my details on a fake GitHub page?
Change the password from a clean device, sign out all sessions, review mailbox rules and connected apps for anything you did not create, and turn on multi-factor authentication. Tell your IT team, because stolen mailbox logins are often used to attack colleagues next.
How do I report a fake GitHub website or message?
Forward phishing emails to reportphishing@apwg.org, report scams at reportfraud.ftc.gov, and report the page to Google Safe Browsing. Also tell GitHub through the contact options on its official website (github.com).
Is it safe to visit the domains listed on this page?
No. They are shown defanged, with dots in brackets, so they cannot be clicked by accident. Do not type them into a browser. Listings are warnings from automated matching, and some are harmless coincidences.
How does PhishPin find lookalike domains of GitHub?
We read the daily list of newly registered domains (1,050,000 domains over the last 15 days) and flag those that contain the brand name, differ by one character or swap look-alike characters. A match is a warning sign, not proof of abuse.
How can a company protect its own brand from lookalike domains like these?
Publish an enforced DMARC policy so nobody can send mail as your domain, monitor newly registered domains that resemble your name, register the obvious typo domains, and file takedown requests with the registrar, host and browser safe-browsing lists when a fake goes live. PhishPin's free brand audit checks the first three for your domain.
Other tech, email & cloud being impersonated
All tech, email & cloud brands ranked