siyabhatia05.github.io is a Netflix impersonation page detected by PhishDestroy on 2026-09-15. Risk: critical (80/100). Registrar: GitHub Pages. Status: Content unavailable. Hosting: Fastly, Inc. VirusTotal: 9/89 engines flag it. Do not enter credentials or connect a wallet.
siyabhatia05.github.io was a phishing page posing as Netflix, hosted on a free GitHub Pages project subdomain and aimed at Netflix subscribers. PhishDestroy first flagged it on 2026-09-15. It went offline the next day, on 2026-09-16, and was still dead when last checked on 2026-10-19, with nothing served at the root.
How the scam works
The page carried the bare title "netflix" and imitated the streaming service's look so a visitor arriving from a text or email lure would assume they were on a real Netflix screen. Pages like this usually claim an account problem or failed payment, then ask the visitor to sign in and "update" billing details. Anything typed in goes straight to the operator. That includes the email, password and full card number with expiry and security code. Victims risk account takeover, fraudulent card charges and reuse of the stolen password on other services.
Evidence
On 2026-09-17, nine of 89 VirusTotal engines flagged the page, among them Netcraft, Sophos, Fortinet, Forcepoint ThreatSeeker, Emsisoft, G-Data, Gridinsoft and alphaMountain.ai. That is a modest count, but the vendors are independent and specialise in phishing detection. urlscan.io independently returned a malicious verdict and recognised Netflix branding on the page. The site is listed on the PhishDestroy blocklist.
Infrastructure
No domain was purchased for this page. It lived on a GitHub Pages subdomain, which costs nothing to create and borrows the trust of a well-known platform's address. Traffic was served through Fastly's content delivery network in the US at 185.199.111.153, which is shared GitHub Pages infrastructure rather than anything controlled by the operator. The page lasted roughly a day after PhishDestroy spotted it, a typical lifespan for throwaway pages on free hosting.
What to do
If you entered your Netflix login here, change the Netflix password right away, sign out all devices from account settings, and change the password anywhere else you reused it. If you entered card details, call your bank to block the card and dispute any charges you don't recognise, and watch statements for small test transactions. Treat any follow-up message "from Netflix" with suspicion and reach your account only through the official app or by typing the address yourself. Defenders should block the hostname and report similar github.io pages to GitHub. They should also alert on login pages that copy Netflix branding while sitting on free hosting platforms.
No. PhishDestroy classifies siyabhatia05.github.io as a Netflix impersonation page (risk: critical, 80/100); it was first detected on 2026-09-15. VirusTotal: 9/89 engines flag it. Treat the site as unsafe.
Is siyabhatia05.github.io safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on siyabhatia05.github.io. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
What should I do if I used siyabhatia05.github.io?
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Edge-IP reputation is not attributed to this domain.
Nameservers 5
ns-692.awsdns-22.net
ns-1622.awsdns-10.co.uk
dns1.p05.nsone.net
dns2.p05.nsone.net
dns3.p05.nsone.net
Location describes the IP network.
TLS certificate
Issuer
YR1
Valid from
2026-08-02 23:38:02
Valid until
2026-10-31 23:38:01
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintf2f9a159ce50a0a168b3eaeaf2fced5addd49ba38e2bf63248f057a139fc7856Certificate names · 6 SANs
*.github.com
*.github.io
*.githubusercontent.com
github.com
github.io
githubusercontent.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Fastly is a cloud computing services provider. Fastly's cloud platform provides a content delivery network, Internet security services, load balancing, and video & streaming services.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · siyabhatia05.github.io
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
3 evidence signal groups linked0 stored notification recordsContent unavailable
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including siyabhatia05.github.io)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.
