Skip to security report
Analytics Dashboard
Domain security and threat intelligence
ueya.mx favicon

ueya.mx

In short

ueya.mx is a Wetransfer impersonation page detected by PhishDestroy on 2026-10-11. Risk: critical (95/100). Registrar: AKKY ONLINE SOLUTIONS. Status: Last known active. Hosting: ORACLE-BMC-31898 - Oracle Corporation, US. VirusTotal: 8/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

“Not Acceptable!”

Registrar
AKKY ONLINE SOLUTIONS
Resolved IP
108.179.194.83
Registered
Feb 21, 2025
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 8/92 Spamhaus DBL: DBL_ABUSED_PHISH Automated brand label: Wetransfer
OTX: 5 refs Oct 11, 2026
API
This domain has been flagged as malicious
Security engines reporting a detection: 8. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
8 / 92
engine detections
Google Safe Browsing
No threat flag
OTX
5
community references
Page captures
9
open gallery
Domain age
608 days
Source evidenceVirusTotal 8 / 92 · OTX 5 references 6 sources

VirusTotal

8 / 92 engine detections

Open report

Spamhaus DBL

DBL_ABUSED_PHISH

OTX

5 community references

Open report

Google Safe Browsing

No threat flag

Open report

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

Analysis

Critical
VirusTotal
8 / 92
OTX
5 community refs
Page captures
9
Page captures Source results Registration record

PhishDestroy threat report

Overview

ueya.mx is a phishing page that imitates WeTransfer. It targets people who receive what looks like a file-sharing notice and expect to download a document. PhishDestroy first flagged it on 2026-10-11, and it was still online with live content when last checked on 2026-10-19. The page title reads "Not Acceptable!", which looks like a server error message, while our classification is WeTransfer impersonation.

How the scam works

WeTransfer lures usually start with an email or message saying files are waiting. The link opens a page styled like a WeTransfer download screen. Before the "files" can be opened, the visitor is asked to sign in, often with their email or work account password. Whatever is typed goes to the operators. A stolen mailbox can then be used to reset other passwords, read invoices and send the same lure to the victim's contacts.

Evidence

On 2026-10-12, eight of 92 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, G-Data, MalwareURL, SOCRadar, Sophos and URLQuery. That is a modest count, but it comes from vendors with separate detection pipelines. urlscan.io rated the page malicious and recognised WeTransfer branding on it. Spamhaus DBL lists the domain as DBL_ABUSED_PHISH, and it appears in five AlienVault OTX threat pulses. It is also on the PhishDestroy blocklist.

Infrastructure

The domain was registered on 2025-02-21 through AKKY ONLINE SOLUTIONS, S.A. DE C.V., about twenty months before PhishDestroy detected the phishing. That long gap fits Spamhaus's "abused" category, which marks domains that existed before phishing content appeared on them. The site resolves to 108.179.194.83 on the Oracle Corporation network (ORACLE-BMC-31898), geolocated to Mexico.

What to do

If you entered a password on this page, change it right away, starting with your email account. Change it anywhere else you reused it. Turn on two-factor authentication and sign out of all active sessions. Check your mailbox for new forwarding rules or filters you did not create, and warn your contacts, since compromised inboxes often send the same lure onward. Do not trust a WeTransfer link unless the sender confirms it through a separate channel. Defenders should block ueya.mx at the mail and web gateway and search logs for clicks or submissions to it. Report the domain to the registrar and hosting provider so the page can be removed.

Useful links

urlscan.io scan and screenshotVirusTotal reportGoogle Safe Browsing statusArchived copyReport phishing to GoogleSite owner? Request a review

Collected source details

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

URLScan · 2026-10-11T12:22:29Z

Observed: · Retrieved:

Uuid
01a12aea-0767-777b-a7ff-deb64b8360b2
Final url
https://ueya.mx/tress/4/
Status
200
Redirected
same-domain
Redirects
[
    {
        "to": "https://ueya.mx/tress/4",
        "from": "http://ueya.mx/tress/4",
        "status": 307
    },
    {
        "to": "https://ueya.mx/tress/4/",
        "from": "https://ueya.mx/tress/4",
        "status": 301
    }
]
Ip
108.179.194.83
Ptr
108-179-194-83.unifiedlayer.com
Contacted domains
[
    "cdn.wetransfer.net"
]
Contacted IP addresses
[
    "108.138.64.107",
    "108.179.194.83"
]
Asns
[
    "16509",
    "31898"
]
Countries
[
    "US",
    "MX"
]
Document hash
2973b510c57b76c0cff48ab34fbf3ba845594187282869a79bc2e42d08175638
Script hashes
[
    "7a3302c0026d1433f41e4b0d218981000e06fac22528ce7f04fa681d907d96da"
]
Globals
[
    "delayTrans",
    "weTransfer",
    "transCounter"
]
Tls
{
    "san": [
        "*.master.card.grant.ueya.mx",
        "*.ueya.mx",
        "master.card.grant.ueya.mx",
        "master.card.grants.ueya.mx",
        "ueya.mx",
        "www.master.card.grants.ueya.mx"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR1",
    "subject": "ueya.mx",
    "protocol": "TLS 1.3",
    "valid_to": "2026-11-23T10:46:30Z",
    "valid_from": "2026-08-25T10:46:31Z"
}
Domain age days
306
Apex age days
306
Tls age days
47
Tls valid days
89
Requests
5
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 94,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "wetransfer"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "WeTransfer"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "Apache",
    "content-type": "text/html"
}
Cloudflare Radar · 2026-10-12T09:39:25Z

Observed: · Retrieved:

Uuid
1c9265e3-ed24-4dfa-b089-321ac3d68aaa
Final url
https://ueya.mx/
Status
200
History
[
    {
        "url": "https://ueya.mx/",
        "status": 200
    }
]
DOM structure hash
30f057954a5d38e6d9aa0e701298bae16a37769516b43b098b2a2d758706cd77
Document hash
24409319851f5b56d7bababd9540276a7fc3501484e72b614dbc810d5be97bbb
Domain risks
[
    "Parked & For Sale Domains",
    "Security Risks"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "ueya.mx",
        "type": "A",
        "value": "108.179.194.83"
    }
]
Dnssec valid
false
Ip
108.179.194.83
Registration record
{
    "registrar": "AKKY ONLINE SOLUTIONS, S.A. DE C.V.",
    "created": "2025-02-21T00:00:00Z",
    "updated": "2026-02-11T00:00:00Z",
    "expires": "2027-02-21T00:00:00Z",
    "nameservers": [
        "ns20.prodns.mx",
        "ns21.prodns.mx"
    ]
}
VirusTotal · 2026-10-18T16:43:22Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 51,
    "malicious": 9,
    "suspicious": 0,
    "undetected": 32
}
Vendor labels
{
    "CRDF": "malicious",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "SOCRadar": "phishing",
    "URLQuery": "malicious",
    "MalwareURL": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "malicious",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Registrar
AKKY ONLINE SOLUTIONS, S.A. DE C.V.
First seen
2025-12-08T15:55:19Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns2.kcg.mx"
    },
    {
        "ttl": 14400,
        "type": "A",
        "value": "108.179.194.83"
    },
    {
        "ttl": 14400,
        "type": "TXT",
        "value": "v=spf1 +a +mx +ip4:108.179.194.80 +include:websitewelcome.com ~all"
    },
    {
        "ttl": 14400,
        "type": "MX",
        "value": "SMTP.GOOGLE.COM",
        "priority": 1
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns1.kcg.mx"
    },
    {
        "ttl": 14400,
        "type": "TXT",
        "value": "google-site-verification=TSlPp2DA-MlN4yrs7D_o7j0VKiWs3saJrwXEU9jf3ZI"
    },
    {
        "ttl": 21600,
        "type": "SOA",
        "rname": "sistemas.kcg.mx",
        "value": "ns1.kcg.mx"
    }
]
Dns at
2026-10-18T16:43:38Z
Jarm
29d29d15d29d29d00042d42d000000cd600c085f371f8533aaf66051f8e5b1
Certificate
{
    "san": [
        "*.master.card.grant.ueya.mx",
        "*.ueya.mx",
        "master.card.grant.ueya.mx",
        "master.card.grants.ueya.mx",
        "ueya.mx",
        "www.master.card.grants.ueya.mx"
    ],
    "issuer": "Let's Encrypt / YR1",
    "serial": "5574889be9e01221fd4d3977ee8b599fa41",
    "sha256": "f2fabedf2604ead97d2baf1f38d13009b16653be52b3c5e148c31aa3437ea0ec",
    "subject": "ueya.mx",
    "valid_to": "2026-11-23T10:46:30Z",
    "valid_from": "2026-08-25T10:46:31Z"
}
Registration record
{
    "registrar": "AKKY ONLINE SOLUTIONS, S.A. DE C.V."
}

Questions about ueya.mx

Is ueya.mx legit?

No. PhishDestroy classifies ueya.mx as a Wetransfer impersonation page (risk: critical, 95/100); it was first detected on 2026-10-11. VirusTotal: 8/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is ueya.mx safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on ueya.mx. 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 ueya.mx?

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.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 9 captures

Primary capture 1 / 9
SourcePrimary capture
Recorded2026-10-11 12:24 UTC
StateStored capture
Position1 / 9
Open capture Wayback Download

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Wetransfer report ↗
IP Reputation abuse score 0/100 0 reports checked Oct 11, 2026
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar AKKY ONLINE SOLUTIONS
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for ueya.mx →
RegistrationCreated Feb 21, 2025 — Expires Feb 21, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 11, 2026
DOM Analysisanalyzed Oct 11, 2026score 88/100
Submitted URLhttp://ueya.mx/tress/4?… query redacted
Favicon Hash
Observed page title
Not Acceptable!
TLS Certificate
Issued by Let's Encrypt / YR1 · stored validity ends in 31 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
108.179.194.83
Network ASN
AS31898
Organization
Oracle Corporation
Observed location
Monterrey, MX
Server header
Apache

Nameservers 6

  • ns1.kcg.mx
  • ns2.kcg.mx
  • ns20.prodns.mx
  • 108.179.194.81
  • ns21.prodns.mx
  • 108.179.194.82

Mail routing 1 MX record

  • SMTP.GOOGLE.COMpriority 1

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR1
Valid from
2026-08-25 10:46:31
Valid until
2026-11-23 10:46:30
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-11 13:02:03 UTC
Collection source
PhishDestroy collector
Certificate fingerprintf2fabedf2604ead97d2baf1f38d13009b16653be52b3c5e148c31aa3437ea0ec
Certificate names · 3 SANs
  • master.card.grant.ueya.mx
  • master.card.grants.ueya.mx
  • www.master.card.grants.ueya.mx

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 108.179.194.83rapiddns.io

Latest Classified Outcome 2026-10-22 10:38:34 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-22 10:38:34 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-22 10:38:34 UTC last content: 2026-10-22 10:38:34 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.
Recorded subdomains3

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • master.card.grant.ueya.mxDomain record
  • master.card.grants.ueya.mxDomain record
  • www.master.card.grants.ueya.mxDomain record

The original observation time is not recorded for these hostnames.

Technologies · 1 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

8 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
G-Data
MalwareURL
SOCRadar
Sophos
URLQuery

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of ueya.mx · checked Oct 12, 2026

100
Good
Performance
FCP
0.77s
First Contentful Paint
LCP
0.77s
Largest Contentful Paint
CLS
0.044
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.92s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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.

Check for cloaking

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

Page titles differ

alive_content: raw=ok; http=200; via=https_proxy; server=Apache

Browser
Not Acceptable!
Crawler
Site Maintenance - We'll Be Back Soon
ueya.mx
Saved result
Cloaked / Filtered
Stored observation history11

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

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Earlier observations 6
  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  6. Availability monitor · First collection record

    Reachable

Recorded activity

5 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. AlienVault OTX

    5 community references

    View source
  3. VirusTotal

    8/92 engine detections

    View source
  4. Added to PhishDestroy

    ueya.mx

    View source
  5. URLScan

    Page captured

    View source

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 8 det. ChainPatrol URLQuery SSL Labs Certificate hostname mismatch CF Radar Open report OTX 5 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback Archived
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked 0 stored notification records Last known active

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.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 ueya.mx)
  • 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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

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

Request a correction or appeal How PhishDestroy works
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/ueya.mx"
  title="PhishDestroy threat report for ueya.mx"
  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>