To report phishing hosted on GitHub Pages, use GitHub's official abuse reporting guidance and describe the deployed page's deceptive behavior. Include the exact page URL, the identity it claims and the relevant repository or account when you can establish the connection. If the repository is unknown, report the known page through GitHub's linked contact form rather than guessing.
A repository containing phishing-related code is not automatically an active phishing operation. GitHub permits dual-use security research while prohibiting phishing and attempted phishing. For a brand-protection team, the useful distinction is what a specific deployment or account is doing, not whether a project contains a suspicious word.
Separate active deception from research
GitHub's Acceptable Use Policies prohibit phishing or attempted phishing. Its active malware or exploits policy separately allows dual-use content used for research into vulnerabilities, malware or exploits.
Those rules make context essential. A research repository may contain a copied sign-in design to document a threat. A deployed page may use the same design to solicit credentials from people who believe they are visiting your organization. The code's appearance alone does not establish which situation you have found.
Assess the evidence in three parts:
- Claimed identity. What organization, service or person does the page claim to represent? Record visible disclaimers and surrounding context as well as copied branding.
- Requested action. Does it ask a visitor to sign in, provide a payment, install something or contact an alleged support agent? Describe the request without completing it.
- Observed use. How did someone reach the page? Preserve a reported lure or referral when available. Distinguish a confirmed observation from an inference about a campaign.
GitHub's impersonation policy prohibits misleading representations of identity or association, but says a similar username is not necessarily impersonation. Include the false affiliation, not merely the name match.
Distinguish the repository from the deployed page
GitHub Pages publishes a website from repository content. GitHub documents different default locations for account-level and project-level sites, and supports custom domains. A repository URL and a deployed website URL therefore identify different things.
Keep both in the case when known. The page records what a visitor encountered. The repository may help locate the source or account for review, but do not assume its current files exactly reproduce the captured deployment.
Use these recommended evidence fields:
- Exact deployed URL, including the path that displayed the suspicious content.
- Observation date, time and timezone.
- Repository URL and account or organization URL, if verified.
- How the page-to-repository relationship was established.
- Whether the page used a default Pages address or a custom domain.
- Any uncertainty about ownership, source visibility or the deployment relationship.
A custom domain can make the hosting relationship less obvious. A copied GitHub logo, a link to a repository or a similar account name does not prove that GitHub hosts the page. If the relationship is uncertain, describe the uncertainty and retain the evidence you actually have.
Build an active-use evidence packet
Collect evidence through your approved investigation process. Do not ask employees or customers to revisit the page, execute repository code or enter credentials to prove the threat exists.
The packet should connect the claimed identity to the requested action. A screenshot of a familiar logo says less than a capture showing the logo, the false support claim and the sign-in request together. Preserve the original capture and explain any redaction in the copy submitted for review.
Include a genuine first-party comparison source, such as the organization's official support or sign-in location. Have the responsible brand owner confirm that the reported presence is not an authorized project, partner page or internal exercise.
For a hypothetical case, the supported finding might be that an unrecognized Pages URL presents itself as the company's support portal and requests account credentials. That observation supports reporting suspected phishing. It does not, by itself, prove that credentials were collected, identify the operator or establish that every repository under the same account is malicious.
If approved analysis identifies an external destination, record it separately with the observation that connects it to the page. Do not include customer secrets, session tokens or unrelated private correspondence in a broadly shared report. Keep complete originals in restricted evidence storage.
Choose the official reporting route
GitHub's reporting documentation provides object-specific controls and a general contact form. Use the route that matches the content you can identify:
Known repository. Open its main page and choose Report repository under the About section. Complete the contact form with the behavior and supporting evidence.
Deceptive user or organization. GitHub documents Block or Report on a user's profile and Report abuse on an organization's main page. Explain the account-level misrepresentation and include the relevant page or repository links.
Pages URL with no verified repository. Use the contact form linked from the official reporting guide. Give the exact deployed URL and explain that the source repository has not been identified. An unknown relationship is better than a confident accusation against the wrong project.
An issue, discussion or comment distributing the lure. Preserve its direct link and use the available reporting control. GitHub limits some reporting functions by role and repository participation. Its documentation distinguishes reporting to repository administrators from reporting to GitHub Support; record which recipient you selected.
Do not post a public issue containing victim data or live malicious links as a substitute for a private abuse report. GitHub's active-malware policy recommends that researchers provide an abuse contact, but does not make contacting the maintainer a prerequisite to a GitHub report. Use judgment about contacting a party that may be involved in the suspected abuse.
Request action on the supported violation
Explain the specific behavior you want reviewed. A report about an active cloned page should identify that deployment and its deceptive request. It should not ask GitHub to remove all security research that contains related code.
GitHub says that, in rare cases of widespread abuse of dual-use content, it may restrict a specific instance to disrupt an ongoing unlawful attack or malware campaign. Its policy describes restrictions that can include authentication requirements or, as a last resort, disabling access or removal. Restrictions may be temporary where feasible.
That is not a promise that a report will result in deletion. Keep the requested scope, submitted evidence and platform decision separate. If a response asks for more information, address the missing fact rather than repeating the original accusation.
Verify the page and connected destinations separately
Retain the submission date, affected URLs and any case reference. After a response, recheck the exact reported page through approved methods. Record whether it still displays the deceptive content, requires authentication, redirects elsewhere or is unavailable. Do not infer the enforcement reason from a failed load alone.
If an external collection destination remains accessible, assign its investigation separately. If a repository remains visible after the deployed page becomes unavailable, record both facts rather than calling the whole report unsuccessful or the whole campaign removed.
Outtake Brand Protection connects cloned visual identities with related infrastructure and external remediation workflows. The relevant next step is connecting the reported page to the wider impersonation case. GitHub still determines the action under its policies; this guide does not imply a particular GitHub integration or guaranteed removal.
For the broader evidence model, read the brand impersonation guide. For provider responsibilities and outcome verification, see the phishing takedown guide.
Sources
- GitHub, Reporting abuse or spam.
- GitHub, Acceptable Use Policies.
- GitHub, Active Malware or Exploits.
- GitHub, Impersonation.
- GitHub, What is GitHub Pages?.
- Outtake, Brand Protection.
Sources reviewed October 9, 2026. Follow the current official controls and policy when submitting a report.