ubiipagos--prestamoubii000.replit.app is a MetaMask impersonation page detected by PhishDestroy on 2026-09-17. Risk: critical (85/100). Registrar: Nom-IQ. Status: Last known active. Hosting: Google LLC. VirusTotal: 5/89 engines flag it. Do not enter credentials or connect a wallet.
Security engines reporting a detection: 5. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
ubiipagos--prestamoubii000.replit.app is an impersonation phishing page hosted on Replit's shared app platform. Its hostname combines the Ubii Pagos payment brand with "prestamo", Spanish for loan, which points to Spanish-speaking Ubii users looking for quick credit. PhishDestroy first flagged it on 2026-09-17. As of 2026-10-19 the site was still online and returning a redirect.
How the scam works
Fake loan pages built on a payment brand's name usually promise fast approval, then ask for login credentials, card or bank details, ID documents, or an upfront "processing" or "insurance" fee before any money is released. The loan never arrives. The victim loses the fee and hands over an account that can be emptied or reused for further fraud. When we checked, the page title read "This app isn't live yet", Replit's placeholder text, while our classification is impersonation phishing.
Evidence
On 2026-09-23, VirusTotal showed 5 of 89 engines flagging the address: ChainPatrol, alphaMountain.ai, CRDF, Forcepoint ThreatSeeker and LevelBlue. That count is low, so most security tools will not warn visitors. The page also appears on the PhishDestroy, MetaMask and SEAL blocklists, which gives wallet users and browser extensions that consume those lists a second layer of protection.
Infrastructure
The 2021-04-16 registration date and the Nom-IQ Limited dba Com Laude registrar belong to Replit's parent domain, not to the operator. Anyone can create a subdomain like this in minutes at no cost. Traffic is served from Google LLC infrastructure in the US, and the Google Trust Services certificate is issued automatically to every Replit app. The padlock in the browser therefore says nothing about who runs the page.
What to do
Ubii Pagos does not lend money through Replit subdomains, so treat any loan offer here as fraudulent and never pay an advance fee. If you entered a Ubii password, change it from the official app and enable two-factor authentication. If you shared card or bank details, contact your bank to block the card and dispute charges. If you uploaded ID documents, watch for accounts opened in your name. Defenders should block the full hostname, report it to Replit's abuse team, and alert Ubii's security contacts so they can warn customers.
Questions about ubiipagos--prestamoubii000.replit.app
Is ubiipagos--prestamoubii000.replit.app legit?
No. PhishDestroy classifies ubiipagos--prestamoubii000.replit.app as a MetaMask impersonation page (risk: critical, 85/100); it was first detected on 2026-09-17. VirusTotal: 5/89 engines flag it. Treat the site as unsafe.
Is ubiipagos--prestamoubii000.replit.app safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on ubiipagos--prestamoubii000.replit.app. 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 ubiipagos--prestamoubii000.replit.app?
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.
For the registrable domain replit.app behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
34.117.33.233
Network ASN
AS396982
Organization
Google Cloud
Observed location
Kansas City, US
Nameservers 1
ns-cloud-b4.googledomains.com
Location describes the IP network.
TLS certificate
Issuer
Google Trust Services / WR3
Valid from
2026-09-02 11:30:15
Valid until
2026-12-01 12:25:50
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-21 13:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint4a74494d584027de8f1b50d93d1683733368fbaea4298191709beefd53e0b0aeCertificate names · 1 SAN
replit.app
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-23 10:07:31 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-23 10:07:31 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 · 3 identified
Google Cloud
IaaS
Google Cloud is a suite of cloud computing services.
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.
Content matches8
Same favicon hash or the same page title as this host.
3 evidence signal groups linked0 stored notification recordsLast 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.
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 ubiipagos--prestamoubii000.replit.app)
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.
