Skip to security report
meharislivegamingyoutube.github.io favicon
Domain security and threat intelligence

meharislivegamingyoutube.github.io

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

The page at meharislivegamingyoutube.github.io mimics a genuine Google OAuth consent prompt to trick visitors into linking an unauthorized application called Mehar Gaming to their Google account. If you already submitted credentials or approved this access, immediately revoke the app's permissions in your Google account settings and change your password.

More about the sources
Recorded security signals

Stored VirusTotal result: 16/92 engines flagged. Malicious: 14. Suspicious: 2. Analysis time (as stored): 2026-11-17 09:28 UTC. Retrieved (as stored): 2026-11-18 09:56 UTC. Listed by external blocklists: PhishFeed. Use caution — do not enter credentials or personal information.

VirusTotal detections: 16/92 Stored blocklist matches: 1 Google Safe Browsing: threat flag recorded
Registrar
GitHub
Resolved IP
United States185.199.108.153GitHub, Inc · CDN
First seen by PhishDestroy
2026-11-18
URLScan
Page captures
open gallery
2026-11-18 CDN

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

Domain summary

PhishDestroy first recorded meharislivegamingyoutube.github.io on 2026-11-18. Stored VirusTotal result: 16/92 engines flagged. Malicious: 14. Suspicious: 2. Analysis time (as stored): 2026-11-17 09:28 UTC. Retrieved (as stored): 2026-11-18 09:56 UTC. Google Safe Browsing flags it. Risk: critical (evidence score 100/100). Registrar: GitHub. Status: HTTP 404 · Content unavailable. Hosting: Fastly, Inc. Listed by external blocklists: PhishFeed. Do not enter credentials or connect a wallet.

Critical
Status
HTTP 404 · Content unavailable
VirusTotal
16 / 92
Blocklist matches
1 external + PhishDestroy list
Hosting
United States185.199.108.153GitHub, Inc · CDN
Registrar
GitHub
Page captures
9

URLScan capture · 2026-11-18 05:28 UTC · SHA-256 da3c9507…22bd6c6

PhishDestroy analysis, reviewed version

Page layout and OAuth deception

The page displays a clean, minimalist layout modelled closely after genuine Google account authentication screens. At the top left sits the standard Google logo, while the central section features a prominent red YouTube-style play icon above the bold heading "Continue to Mehar Gaming". Beneath this, explanatory text states that "Mehar Gaming wants to access your Google Account", accompanied by a mock account selector box displaying "Google User" and a placeholder email address. A secondary button allows visitors to "Use another account", alongside standard fine print referencing Google's privacy policy and terms of service. At the very bottom, interactive buttons labeled "Cancel" and a blue "Continue" button invite the user to proceed with the authorization request.

Credential harvesting and security status

urlscan classified the page as malicious, Google Safe Browsing flags it, and OpenPhish blocks it, which confirms that the site is actively monitored for malicious behaviour rather than operating as a legitimate service. PhishDestroy's evidence score for it is 40/100 (high), reflecting the high risk associated with unauthorized OAuth applications hosted on public developer platforms like GitHub. By mimicking authentic single sign-on dialogs, the page exploits user trust in familiar authentication flows to trick visitors into granting third-party access to their personal accounts.

Recommended actions for visitors

Visitors who reached this page should close the browser tab immediately and avoid clicking any buttons or entering passwords. Anyone who has already interacted with the prompt and authorized the application must navigate directly to their Google account security settings, locate connected third-party apps, and revoke all permissions granted to Mehar Gaming. Additionally, affected users should update their account password and review recent security activity for unauthorized access.

Source evidenceVirusTotal 16 / 92 · Google Safe Browsing: flagged 6 sources

VirusTotal

16 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 14 fields
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

Source
VirusTotal
Result state
observed
Numerator
16
Denominator
92
Vendors
alphaMountain.ai, BitDefender, DNS8, ESET, Emsisoft, Forcepoint ThreatSeeker, Fortinet, G-Data, Google Safe Browsing, Lionic, MalwareURL, Netcraft, SOCRadar, Sophos, URLQuery, Webroot
Observed at
2026-11-17 09:28:52
Checked at
2026-11-18 10:56:46
Fetched at
2026-11-18 09:56:46

Google Safe Browsing

Threat flag recorded

Open report

URLScan

Malicious

SHA-256 6dbd06b3…aa20a1b

Open report
URLScanOriginal source recordObserved: 20 fields
Separate monitor record · 2026-11-19 04:30 UTC

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

UUID
01a1ee06-b80a-7228-8e25-b4b5b4bb9cbf
Score
100
Malicious
✓
Result at
2026-11-19T04:30:21Z
Enriched at
2026-11-19T09:13:04Z
Source timestamps
Urlscan result at: 2026-11-19 05:30:21; Urlscan enriched at: 2026-11-19 10:13:04

PhishDestroy DOM

10 / 100 · heuristic score · 2 brand references · 0 classifications

Content heuristic only; not the final score

Open report
Page code check by a separate monitor · 10 / 100 · 2026-11-18 10:00 UTC

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

Heuristic score
10
Analyzed at
2026-11-18T10:00:04Z
Source timestamp
2026-11-18 11:00:04
Technical metadata

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

AI title
meharislivegamingyoutube.github.io — Fake Google OAuth page
AI description
meharislivegamingyoutube.github.io shows a fake Google sign-in page for Mehar Gaming, flagged by urlscan and Google Safe Browsing. Do not submit your password.
AI summary
Page layout and OAuth deception The page displays a clean, minimalist layout modelled closely after genuine Google account authentication screens. At the top left sits the standard Google logo, while the central section features a prominent red YouTube-style play icon above the bold heading "Continue to Mehar Gaming". Beneath this, explanatory text states that "Mehar Gaming wants to access your Google Account", accompanied by a mock account selector box displaying "Google User" and a placeholder email address. A secondary button allows visitors to "Use another account", alongside standard fine print referencing Google's privacy policy and terms of service. At the very bottom, interactive buttons labeled "Cancel" and a blue "Continue" button invite the user to proceed with the authorization request. Credential harvesting and security status urlscan classified the page as malicious, Google Safe Browsing flags it, and OpenPhish blocks it, which confirms that the site is actively monitored for malicious behaviour rather than operating as a legitimate service. PhishDestroy's evidence score for it is 40/100 (high), reflecting the high risk associated with unauthorized OAuth applications hosted on public developer platforms like GitHub. By mimicking authentic single sign-on dialogs, the page exploits user trust in familiar authentication flows to trick visitors into granting third-party access to their personal accounts. Recommended actions for visitors Visitors who reached this page should close the browser tab immediately and avoid clicking any buttons or entering passwords. Anyone who has already interacted with the prompt and authorized the application must navigate directly to their Google account security settings, locate connected third-party apps, and revoke all permissions granted to Mehar Gaming. Additionally, affected users should update their account password and review recent security activity for unauthorized access.
AI generated by
threat-v10-gemini
AI generated at
2026-11-18T09:45:43Z
Revision
4bf872bb13ae54e1cec52d050a27440d5ee3f6bff71489feac4cb75a06734075
Mode
reviewed
Interpretation
Selected public package; text generation time is separate from source observation dates.

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 16 fields

Mail configuration

SPF lookups
0

CAA records

Count
6
Domain
meharislivegamingyoutube.github.io
Allowed issuers
  • letsencrypt.org
  • sectigo.com
  • digicert.com

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

TLS connection

ALPN
h2
Cipher
TLS_AES_128_GCM_SHA256
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443

DNS servers

Nameservers
  • IP address
    205.251.194.180
    Host
    ns-692.awsdns-22.net
  • IP address
    198.51.44.5
    Host
    dns1.p05.nsone.net
  • IP address
    198.51.45.5
    Host
    dns2.p05.nsone.net
  • IP address
    198.51.44.69
    Host
    dns3.p05.nsone.net
  • IP address
    198.51.45.69
    Host
    dns4.p05.nsone.net
  • IP address
    205.251.197.59
    Host
    ns-1339.awsdns-39.org
  • IP address
    205.251.198.86
    Host
    ns-1622.awsdns-10.co.uk
  • IP address
    205.251.193.137
    Host
    ns-393.awsdns-49.com
DNS zone
github.io

Page quality

Layout shift (CLS)
0
SEO score
82
Speed Index, s
0.79
First Contentful Paint (FCP), s
0.79
Largest Contentful Paint (LCP), s
0.79
Total Blocking Time (TBT), ms
0
Performance score
100
Accessibility score
55
Best practices score
92

Location

IP address
2606:50c0:8002::153
ASN
54113
Organization
Fastly, Inc.
City
San Francisco
Country
US

TLS certificate

Subject alternative names
  • *.github.com
  • *.github.io
  • *.githubusercontent.com
  • github.com
  • github.io
  • githubusercontent.com
Key size, bits
2048
Certificate chain
  • *.github.io
  • YR1
  • Root YR
  • ISRG Root X1
Issuer
Let's Encrypt / YR1
Serial
06A65E5D3279BA564A4DE74EB5D64478DBB8
SHA-256
f2f9a159ce50a0a168b3eaeaf2fced5addd49ba38e2bf63248f057a139fc7856
Subject
*.github.io
Valid until
Valid from

DNS records

A
  • 185.199.109.153
  • 185.199.108.153
  • 185.199.111.153
  • 185.199.110.153
AAAA
  • 2606:50c0:8003::153
  • 2606:50c0:8002::153
  • 2606:50c0:8001::153
  • 2606:50c0:8000::153

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
2606:50c0:8002::153
IP version
6

Technology stack

Technologies
  • Varnish
  • GitHub Pages
  • Fastly

HTTP headers

Response headers
Server
GitHub.com
Content-Type
text/html; charset=utf-8
Content-Security-Policy
default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'
Via
1.1 varnish
X-Cache
HIT
X-Cache-Hits
2
X-Served-By
cache-fra-eddf8230210-FRA
Original source fields · JSON
Mail configuration
Spf lookups: 0
Caa records
Count: 6; Domain: meharislivegamingyoutube.github.io; Issuers: letsencrypt.org, sectigo.com, digicert.com
Protective DNS results
Resolvers: 12; Blocked count: 0
TLS connection
Alpn: h2; Cipher: TLS_AES_128_GCM_SHA256; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443
DNS server
NS: (IP: 205.251.194.180; Host: ns-692.awsdns-22.net), (IP: 198.51.44.5; Host: dns1.p05.nsone.net), (IP: 198.51.45.5; Host: dns2.p05.nsone.net), (IP: 198.51.44.69; Host: dns3.p05.nsone.net), (IP: 198.51.45.69; Host: dns4.p05.nsone.net), (IP: 205.251.197.59; Host: ns-1339.awsdns-39.org), (IP: 205.251.198.86; Host: ns-1622.awsdns-10.co.uk), (IP: 205.251.193.137; Host: ns-393.awsdns-49.com); Zone: github.io
Quality
Cls: 0; Seo: 82; Si s: 0.79; Fcp s: 0.79; Lcp s: 0.79; Tbt ms: 0; Performance: 100; Accessibility: 55; Best practices: 92
Location
IP: 2606:50c0:8002::153; ASN: 54113; Org: Fastly, Inc.; City: San Francisco; Country: US
SSL
San: *.github.com, *.github.io, *.githubusercontent.com, github.com, github.io, githubusercontent.com; Bits: 2048; Chain: *.github.io, YR1, Root YR, ISRG Root X1; Issuer: Let's Encrypt / YR1; Serial: 06A65E5D3279BA564A4DE74EB5D64478DBB8; SHA256: f2f9a159ce50a0a168b3eaeaf2fced5addd49ba38e2bf63248f057a139fc7856; Subject: *.github.io; Valid to: 2026-12-29T23:44:45Z; Valid from: 2026-09-30T23:44:46Z
DNS records
A: 185.199.109.153, 185.199.108.153, 185.199.111.153, 185.199.110.153; Aaaa: 2606:50c0:8003::153, 2606:50c0:8002::153, 2606:50c0:8001::153, 2606:50c0:8000::153
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Message: Site does not serve any HSTS headers.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Get IP
IP: 2606:50c0:8002::153; Family: 6
Tech stack
Technologies: Varnish, GitHub Pages, Fastly
HTTP headers
Headers: Server: GitHub.com; Content type: text/html; charset=utf-8; Content security policy: default-src 'none'; style-src 'unsafe-inline'; img-src data:; connect-src 'self'; Via: 1.1 varnish; X cache: HIT; X cache hits: 2; X served by: cache-fra-eddf8230210-FRA

Questions about meharislivegamingyoutube.github.io

Is meharislivegamingyoutube.github.io affiliated with Google?

No, this domain has no connection to Google. It is hosted on GitHub Pages to impersonate official authentication flows and deceive visitors.

What happens if I clicked Continue on the page?

Clicking continue may grant an unauthorized third-party application access to your Google account data and profile information. You should revoke permissions immediately in your Google account settings.

How can I check if my account was compromised?

Review your Google account's recent security activity, check for unfamiliar connected applications or devices, and change your password if you notice any unauthorized changes.

Explore

Blocklist matches1 external + PhishDestroy list · PhishDestroy · PhishFeed 1
PhishDestroy PhishDestroy list View source
PhishFeed Listed View source

Last checked

Page captures (9)

All capture links and hashes (9)

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Google report ↗
Google Safe Browsing Flagged Social engineering checked 2026-11-22
IP Context United States185.199.108.153 Fastly shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider GitHub
Abuse contactabuse@github.com
HTTP Status404 Not Found
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-11-18
DOM Analysisanalyzed 2026-11-18score 10/1002 brand signals
Submitted URLhttp://meharislivegamingyoutube.github.io/meharislivegamingyoutube-meharislivegamingyoutube-Meharisliveyoutube.com
Observed page title
Site not found · GitHub Pages
Automated brand references
Gmail Google
TLS Certificate
Issued by YR1 · stored validity ends in 37 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United States185.199.108.153
Network ASN
AS54113
AS name
FASTLY - Fastly, Inc., US
Organization
GitHub, Inc
Observed location
United StatesSan Francisco, US
Server header
GitHub.com

Edge-IP reputation is not attributed to this domain.

Nameservers 8

  • dns1.p05.nsone.net
  • dns2.p05.nsone.net
  • dns3.p05.nsone.net
  • dns4.p05.nsone.net
  • ns-1339.awsdns-39.org
  • ns-1622.awsdns-10.co.uk
  • ns-393.awsdns-49.com
  • ns-692.awsdns-22.net

Location describes the IP network.

TLS certificate

Issuer
YR1
Valid from
2026-09-30 23:44:46
Valid until
2026-12-29 23:44:45
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintf2f9a159ce50a0a168b3eaeaf2fced5addd49ba38e2bf63248f057a139fc7856
Certificate 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.

Latest Classified Outcome 2026-11-22 11:14 UTC

No phishing content was served at the latest check.

Technical details
Primary outcome Inactive reason: Http No Content 70% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Root path has no content Content: Absent At Root DNS: Stale
Latest HTTP observation Inactive Http No Content 70% 2026-11-22 11:14 UTC
RDAP registration
Observed timeline last reachable: 2026-11-18 09:40 UTC current episode first observed: 2026-11-19 00:08 UTC observed RIP window: 2026-11-18 09:40 UTC → 2026-11-19 00:08 UTC · 14.46h midpoint estimate ≈ 2026-11-18 16:54 UTC · precision medium · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 3 identified
Open complete records

VirusTotal Analysis

16 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive result retrieved by PhishDestroy
DNS8
ESET
G-Data
Lionic
Sophos
Webroot
Emsisoft
Fortinet
Netcraft
SOCRadar
URLQuery
MalwareURL
BitDefender
alphaMountain.ai
Google Safe Browsing
Forcepoint ThreatSeeker
PageSpeed (mobile): 100

Google PageSpeed Insights — mobile performance audit of meharislivegamingyoutube.github.io ·

100
Good
Performance
FCP
0.79 s
First Contentful Paint
LCP
0.79 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
0.79 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
14.46
Estimate basis
Bounded by observations
Estimate precision
Medium

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

All stored data112
Open complete records

Captured network requests

Network requests: 2 SHA-256 hashes: 2 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-18 09:43 UTC.

Open this scan on URLScan 01a1ee06-b80a-7228-8e25-b4b5b4bb9cbf ↗

Stored observation history3

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    No page content

    no page content in the HTTP response

  2. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  3. Domain monitor · First collection record

    Reachable

All retained availability observations9
Open complete records

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · recorded

Recorded events: 11. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested recorded
  • Threat Ingested
    meharislivegamingyoutube.github.io detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Google Safe Browsing · Blocklist Detection · Automated brand label: Google · Forensic Evidence Collected · Technical Analysis Recorded recorded
Publication & AvailabilityDestroyList Published recorded

Recorded activity

4 entries

Lifecycle

  1. Domain registered
  2. VirusTotal analysis with detections+5001 d 13 h
  3. Added to PhishDestroy+24 h 11 min
  1. Google Safe Browsing

    Threat flag recorded

    +3 d 13 h
  2. Added to PhishDestroy

    meharislivegamingyoutube.github.io

    same minute
  3. URLScan

    Page captured

    +24 h 11 min
  4. VirusTotal

    16/92 engine detections

How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

meharislivegamingyoutube.github.io

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

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.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Downloaded a file — do not open it and scan the device with security software
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed

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 meharislivegamingyoutube.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)
  • Europol — European cybercrime reporting (EU)
  • 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

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

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 →
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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/meharislivegamingyoutube.github.io"
  title="PhishDestroy threat report for meharislivegamingyoutube.github.io"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>