kolkata-fix-frant.surge.sh is a Trust Wallet impersonation page detected by PhishDestroy on 2026-08-31. Risk: critical (93/100). Registrar: Surge.sh. Status: Content unavailable. Hosting: DigitalOcean, LLC. VirusTotal: 11/92 engines flag it. Do not enter credentials or connect a wallet.
Security engines reporting a detection: 11. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
kolkata-fix-frant.surge.sh is a phishing page that impersonates Trust Wallet under the title "Transfer Trust Wallet". It targets people who hold crypto in Trust Wallet and can be talked into a supposed transfer or migration of their wallet. PhishDestroy first flagged it on 2026-08-31. As of 2026-10-19 the site was still online and serving its phishing content.
How the scam works
The title "Transfer Trust Wallet" frames the visit as a routine procedure, such as moving funds or migrating a wallet, so the request that follows looks legitimate. Pages of this kind usually ask the victim to type in their 12- or 24-word recovery phrase or private key to complete the transfer, or to connect their wallet and approve a prompt. Whoever holds a recovery phrase controls the wallet, so the operators can empty it from their own device, often within minutes. Trust Wallet never asks users to submit their recovery phrase on any website.
Evidence
On 2026-10-15, VirusTotal showed 11 of 92 engines flagging the site, including Kaspersky, Fortinet, Forcepoint ThreatSeeker, alphaMountain.ai, Ermes, Gridinsoft, LevelBlue and Lionic. That is a minority of engines, but the detections come from independent vendors with separate detection pipelines. ScamSniffer, a blocklist that focuses on crypto threats, also lists the domain alongside PhishDestroy.
Infrastructure
The page sits on a subdomain of Surge.sh, a free static-site publishing service. Platforms like this let anyone publish a page in seconds without registering their own domain, and the throwaway-looking name fits that pattern. The site resolves to DigitalOcean, LLC infrastructure in Canada. It uses a domain-validated Sectigo certificate, so the browser padlock only shows that the connection is encrypted and says nothing about who runs the page.
What to do
If you entered your recovery phrase or private key on this page, treat the wallet as compromised. Create a new wallet with a new phrase on a trusted device and move any remaining funds there immediately. If you connected a wallet or signed a prompt, revoke token approvals with a reputable approval-checking tool and watch the address for unexpected transfers. Do not respond to anyone offering paid recovery help, as these offers are a common follow-up scam. Defenders should block the full hostname at the DNS and proxy level and report it to Surge.sh and DigitalOcean for takedown.
No. PhishDestroy classifies kolkata-fix-frant.surge.sh as a Trust Wallet impersonation page (risk: critical, 93/100); it was first detected on 2026-08-31. VirusTotal: 11/92 engines flag it. Treat the site as unsafe.
Is kolkata-fix-frant.surge.sh safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on kolkata-fix-frant.surge.sh. 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 kolkata-fix-frant.surge.sh?
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.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedAug 31, 2026
DOM Analysisanalyzed Oct 9, 2026score 93/1001 brand signal
IoC Extractionscanned Sep 1, 20261 wallet · 0 Telegram IoC
Submitted URLhttp://kolkata-fix-frant.surge.sh/
Favicon Hash
Observed page title
Transfer Trust Wallet
Automated brand references
Trust Wallet
TLS Certificate
Issued by Sectigo Limited· stored validity ends in 105 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
159.203.50.177
Network ASN
AS14061
Organization
Digital Ocean
Observed location
Toronto, CA
Server header
Surge
Location describes the IP network.
TLS certificate
Issuer
Sectigo Limited
Valid from
2026-06-01 00:00:00
Valid until
2026-12-16 23:59:59
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-08-31 10:02:03 UTC
Collection source
PhishDestroy collector
Certificate fingerprint97b6f955e414ca95a3c57ecae57c2cba8532736157112d6cc11f56a5a790058aCertificate names · 1 SAN
surge.sh
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
JSDelivr is a free public CDN for open-source projects. It can serve web files directly from the npm registry and GitHub repositories without any configuration.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · kolkata-fix-frant.surge.sh
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.
4 evidence signal groups linked0 stored notification recordsContent unavailable
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 kolkata-fix-frant.surge.sh)
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.
