sessions.baseapp.qa246.ubware.it is a Linea impersonation page detected by PhishDestroy on 2026-09-01. Risk: critical (78/100). Registrar: Register S.p.a. Hosting: Telecom Italia S.p.A. PhishDestroy sent 1 abuse report. VirusTotal: 4/92 engines flag it. Do not enter credentials or connect a wallet.
Security engines reporting a detection: 4. 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@retail.telecomitalia.it.
The latest stored availability evidence still shows the domain reachable; 1 month 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.
sessions.baseapp.qa246.ubware.it is an impersonation phishing page. It is buried several levels deep under an Italian domain and uses "baseapp" and "sessions" in its hostname to pass as a Base App sign-in or session page for crypto wallet users. PhishDestroy first flagged it on 2026-09-01. As of 2026-10-19 the server still answers, but the phishing content is no longer active.
How the scam works
The page title reads only "Redirecting...", a placeholder rather than branded content. We classified the host as impersonation. Pages like this usually act as a relay, briefly showing a redirect notice before sending visitors to a lookalike Base App screen. That screen asks them to reconnect a wallet, restore a session, or enter a recovery phrase. Whatever the victim approves or types goes to the operator, who can then take wallet access or sign transactions that empty the funds.
Evidence
VirusTotal detection is thin: 4 of 92 engines flagged the host as of 2026-10-15. Those engines were alphaMountain.ai, CRDF, Forcepoint ThreatSeeker and SOCRadar. Stronger support comes from the crypto ecosystem itself. Besides PhishDestroy, the host appears on the MetaMask and SEAL blocklists, both curated specifically for wallet-targeting phishing. That means wallet extensions and security tooling that use those lists should already warn visitors.
Infrastructure
The parent domain, ubware.it, was registered on 2015-04-16 through Register S.p.a. That is more than eleven years before this hostname surfaced, so a long-standing domain is lending its age and reputation to a throwaway subdomain. The "qa246" label suggests a test or staging environment that was reused or exposed. Hosting sits on the Telecom Italia S.p.A. network in Italy. The Let's Encrypt certificate only means the page loads with a padlock, which says nothing about whether it is legitimate.
What to do
If you only opened the page, close it and do not return through any link that led you there. If you connected a wallet or signed anything, revoke token approvals and permissions granted around that time using a reputable approval checker. Move remaining assets to a fresh wallet if you are unsure what you signed. If you typed a seed phrase, treat that wallet as compromised and transfer funds out immediately to a new wallet created from a new phrase. Defenders should block the full hostname and keep watching the parent domain for new subdomains using wallet brand names.
No. PhishDestroy classifies sessions.baseapp.qa246.ubware.it as a Linea impersonation page (risk: critical, 78/100); it was first detected on 2026-09-01. VirusTotal: 4/92 engines flag it. Treat the site as unsafe.
Is sessions.baseapp.qa246.ubware.it safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on sessions.baseapp.qa246.ubware.it. 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 sessions.baseapp.qa246.ubware.it?
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.
Certificate fingerprint59ee207b81505b962c7d7dfcdfd411b66c8d40acd84ba05899b306ea8ba17a27Certificate names · 3 SANs
firewall.trevigroup.biz
nextcloud.trevigroupsrl.it
nextcloud.ubware.it
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-22 10:23:33 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-08 10:27:57 UTClast content: 2026-10-08 10:27:57 UTCcurrent episode first observed: 2026-10-08 20:20:32 UTCobserved RIP window: 2026-10-08 10:27:57 UTC → 2026-10-08 20:20:32 UTC · 9.88hmidpoint estimate ≈ 2026-10-08 15:24:14 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.
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.
5 evidence signal groups linked1 stored notification recordsUnverified
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 sessions.baseapp.qa246.ubware.it)
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.
