Skip to security report
Domain security report
metamaskauth.yzz.me favicon

metamaskauth.yzz.me

“Domain Suspended”

Threat verdict
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Cloaked · reachable Reachability observed through cloaking checks Observed · HTTP probe
VirusTotal detections: 13/91 Spamhaus DBL: DBL_PHISH Stored blocklist matches: 2 URLQuery threat systems: 7 alerts Automated brand label: MetaMask Last known active
Jun 27, 2026 MetaMask 1 Report Sent
API
Registrar
Porkbun
Resolved IP
77.72.1.44
Registered
Aug 7, 2022
3 sources
Stored TLS certificateHostname mismatchReview certificate names and collection time
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 13. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@ifastnet.com. The latest stored availability evidence still shows the domain reachable; 3 months has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
3 months
Reports sent
1
Latest case ID
PD-20260627-83F18F
Current status
HTTP 200 at latest stored check

Additional indicators at a glance

Spamhaus DBL
DBL_PHISH
VirusTotal
VirusTotal
13 det.
URLQuery
URLQuery
7 threat alerts
URLScan
URLScan
TLS Certificate
Hostname mismatch -34d
ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2 · Certificate hostname mismatch
Age
4.2 yr
Observed status
Cloaked · reachable 200
PhishDestroy
DestroyList
Listed
Reports Sent
1

Source evidence

9 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

13 / 91

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

URLQuery

7 threat-system alerts

Report
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

Public blocklists

2 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Spamhaus DBL

DBL_PHISH

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

no community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: clean

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

stored report

View stored capture ↗
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analysis completed

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Network Security Intelligence
Threat Detection Systems 7 alerts
Detection System Indicator Verdict Alert
DigiCert UltraDNS metamaskauth.yzz.me malicious Sinkholed
Hagezi Threat Feed metamaskauth.yzz.me malicious Sinkholed
Cloudflare DNS metamaskauth.yzz.me malicious Sinkholed
OpenDNS metamaskauth.yzz.me phishing Phishing Block
Quad9 DNS metamaskauth.yzz.me malicious Sinkholed
DNS4EU metamaskauth.yzz.me malicious Sinkholed
DigiCert UltraDNS suspended-domain.net malicious Sinkholed

Evidence Summary

Critical
VirusTotal
13/91
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

This domain, metamaskauth.yzz.me, operates as a crypto drainer, a type of phishing infrastructure designed to deceive users into connecting their cryptocurrency wallets. Once connected, malicious scripts automatically execute unauthorized transactions, draining funds from the victim’s wallet without consent. The threat primarily targets users of decentralized finance (DeFi) platforms and wallet extensions, exploiting trust in seemingly legitimate authentication prompts. Analysis indicates the domain was registered on August 07, 2022, through Porkbun LLC, and currently resolves to the IP address 185.27.134.34. As of the latest assessment, 12 out of 95 security vendors on VirusTotal have flagged the domain as malicious, confirming its active use in fraudulent campaigns. The domain remains operational, suggesting ongoing exploitation attempts. If a user has interacted with metamaskauth.yzz.me, immediate action is required. First, revoke any wallet connections or permissions granted to the domain via the wallet’s settings interface. Next, transfer remaining assets to a new, secure wallet address not previously exposed to the malicious site. Monitor transaction history for unauthorized activity and report the incident to relevant blockchain security platforms for further investigation. Users should also scan their devices for malware, as crypto drainers may deploy additional payloads to maintain persistence.

Data coverage & collection

21 · datasets with records / 10 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
13 / 91 · engine detections
URLScan analysis
Automated verdict retained
URLQuery
7 · recorded detections / alerts
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
0 · community references
External blocklists
2 · external matches
Cloudflare Radar
cleanCollection time not recorded
Spamhaus DBL
DBL_PHISH
Domain registration
Porkbun LLCCollection time not recorded
Network & DNS
77.72.1.44 · 0 · nameserversCollection time not recorded
TLS certificate
ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2
Page captures
3 · retained captures
Page analysis
1 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
Response records
1 · outgoing report records
Availability history
30 · stored state changes
Lookalike relationships
79 · retained relationshipsCollection time not recorded
Chainabuse records
1 · recorded reports
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 10

These checks have no retained result. This does not mean they passed or that a scan is running.

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • HTML archives
  • Site configuration files
  • PageSpeed performance
  • Recorded subdomains
  • Source observation history
  • Community reports
Download the dated observations and supporting metadata.

Blocklist records

2 · external source matches

Public Blocklist Status

Domain, network & archive

Porkbun LLC · 77.72.1.44 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 0 reports checked Sep 25, 2026
Registrar (base domain) Porkbun (Unknown)
Abuse contactabuse@ifastnet.com
Registration (base domain)yzz.me · Created Aug 7, 2022 — Expires Aug 7, 2026
Cloaking Cloaking Detected Redirect split · score 3/6
alive_content: raw=ok; http=200; via=https_proxy; server=nginx
server: nginx title: DNS Resolution Error - Domain Not Found, Or Domain not added to hosting account
checked Oct 17, 2026
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedJun 27, 2026
DOM Analysisanalyzed Jun 27, 2026score 100/1001 brand signal
Submitted URLhttp://metamaskauth.yzz.me/
Favicon Hash
Case ID

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
77.72.1.44
Network ASN
AS12488
Organization
AS34119 Wildcard UK Limited
Observed location
London, GB
Server header
LiteSpeed

Location describes the IP network.

TLS certificate

Issuer
ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2
Valid from
2026-06-15 00:00:00
Valid until
2026-09-13 23:59:59
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-06-27 01:00:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprint0ef7b2b45d70e4d08839e6190be7d250175f4b9730b1e0b0178949b0f14aea6c
Certificate names · 1 SANs
  • yzz.me

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-10-17 10:18:24 UTC

Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-17 10:18:24 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-17 10:18:24 UTC last content: 2026-10-17 10:18:24 UTC
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 · 6 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

13 / 91 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 19 detections
ChainPatrol
BitDefender
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion evidence

Cloaking confirmed: scanners and visitors see different content

Observed Different content was served to scanners and to visitors

The page served one response to a browser-like visitor and another to a crawler or security scanner. Cloaking exists only to keep reviewers away from the real landing page.

Stored cloaking flag
Observed
Cloaking type
redirect_split
Cloaking score
3/6
Last cloaking scan
Server header seen by scanner
nginx

Scanner note: alive_content: raw=ok; http=200; via=https_proxy; server=nginx

Title shown to the security scannerDNS Resolution Error - Domain Not Found, Or Domain not added to hosting account
Title shown to a browser visitorDomain Suspended
Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
Saved result
Cloaked / Filtered

Timeline & response

1 · outbound report records

Stored observation history30

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

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Earlier observations 25
  1. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  6. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  7. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  8. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  9. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  10. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  11. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  12. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  13. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  14. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  15. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  16. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  17. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  18. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  19. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  20. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  21. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  22. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  23. Availability monitor · Recorded state

    live_content→Unknown

    probe_inconclusive

  24. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  25. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

Threat Response Pipeline

Discovery
Analysis
Notifications
Monitoring

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

Threat Ingested
metamaskauth.yzz.me detected and queued for full analysis
Jun 27, 2026
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
Sep 25, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Jun 27, 2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in Wayback Machine — historical evidence archived
Jun 27, 2026
VirusTotal
13/91 recorded on VirusTotal
Sep 29, 2026
Blocklist Detection
Found in 2 blocklists: MetaMask, SEAL
Oct 17, 2026
Brand Impersonation
Impersonation of MetaMask
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Jun 27, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 17, 2026
Sent Report Recorded
Stored outgoing record associated with registrar Porkbun LLC, 1 abuse contact
abuse@ifastnet.com
Jun 27, 2026
DestroyList Published
Jun 27, 2026
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this observation.
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.

Related infrastructure

Shared hosting, registrar records and related domains

Lookalike domains

79 stored lookalike domains

Show all (67)
metasmask.io insertion Internal report metramask.io insertion Internal report mewtamask.io insertion Internal report mmetamask.io homoglyph Internal report mtamask.io omission Internal report mwetamask.io insertion Internal report nmetamask.io homoglyph Internal report metamark.io bitsquatting Internal report metamaskj.io addition Internal report metammask.io homoglyph Internal report metamnask.io homoglyph Internal report emtamask.io transposition m-etamask.io hyphenation meamask.io omission meatmask.io transposition meramask.io replacement mertamask.io insertion metaamask.io repetition metaamsk.io transposition metaask.io omission metalmask.io insertion metamaask.io insertion metamadsk.io insertion metamaek.io replacement metamak.io omission metamas.io omission metamasak.io insertion metamasdk.io insertion metamask-io.com various metamasl.io replacement metamasm.io replacement metamsak.io transposition metamsk.io omission metamusk.io vowel-swap metamzsk.io replacement metarnask.io homoglyph metmaask.io transposition metmask.io omission metsamask.io insertion metsmask.io replacement mettamask.io repetition metwmask.io replacement metyamask.io insertion metzmask.io replacement meyamask.io replacement meytamask.io insertion mitamask.io vowel-swap mnetamask.io homoglyph mretamask.io insertion mrtamask.io replacement mstamask.io replacement mteamask.io transposition mwtamask.io replacement rnetamask.io homoglyph matamask.io bitsquatting mdtamask.io bitsquatting metamasi.io bitsquatting metamasj.io bitsquatting metamaska.io addition metamaskk.io addition metamaskl.io addition metamaso.io bitsquatting metamesk.io bitsquatting metamqsk.io bitsquatting metemask.io bitsquatting netamask.io homoglyph xn--metamas-bhb.io homoglyph

Community records

Retained community reports and observations

Community intelligence

1 community report

CategoryPHISHING

The PhishFort Detection System has flagged this as a domain threat, classified as null. Threat detected at 2026-06-26T12:31:00.195Z.

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Third-Party Detection — ChainAbuse
1 report filed for metamaskauth.yzz.me · category: Phishing · source checked
Flagged by PhishFort Detection System on Jun 26, 2026 — automated submission, not a user testimony. Source: ChainAbuse (TRM Labs).
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260627-83F18F Recipient: abuse@ifastnet.com
Page title stored with report: Domain Suspended
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
Deep Analysis

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

5 evidence signal groups linked 1 stored notification records Cloaked · reachable
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.

Official reporting routes
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 →
Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

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 metamaskauth.yzz.me)
  • 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

Live Threat Feed Appeal This Listing
Read the evidence in context

About This Report: metamaskauth.yzz.me

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “Domain Suspended”. Apparent target: MetaMask.

VirusTotal detections for metamaskauth.yzz.me: 13 (2026-09-29 02:10:32 UTC).

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

Embed this report

A 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/metamaskauth.yzz.me"
  title="PhishDestroy threat report for metamaskauth.yzz.me"
  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>