The domain kope-two.vercel.app hosted a fraudulent login interface designed to capture account credentials and passwords. Anyone who submitted a password on this page should immediately change their credentials on the actual service provider account.
Page title: “404: NOT_FOUND”
More about the sources
Recorded security signals
Stored VirusTotal result: 9/92 engines flagged. Malicious: 8. Suspicious: 1. Analysis time (as stored): 2026-11-17 11:10 UTC. Retrieved (as stored): 2026-11-18 09:43 UTC. Use caution — do not enter credentials or personal information.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
Analysis
Domain summary
PhishDestroy first recorded kope-two.vercel.app on 2026-11-18. Stored VirusTotal result: 9/92 engines flagged. Malicious: 8. Suspicious: 1. Analysis time (as stored): 2026-11-17 11:10 UTC. Retrieved (as stored): 2026-11-18 09:43 UTC. Risk: critical (evidence score 80/100). Registrar: Vercel. Status: Reachable · access restricted. Hosting: Amazon.com, Inc. Do not enter credentials or connect a wallet.
URLScan capture · 2026-11-18 01:06 UTC · SHA-256 651cb6c6…7afe2e5
PhishDestroy analysis, reviewed version
Page layout and credential input
The page hosted on kope-two.vercel.app presents a modal dialog centered over a grey background displaying standard documentation placeholder text in multiple languages, including English, Arabic, Chinese, French, Russian, and Spanish. A prominent blue email envelope icon sits above a loading bar and the text "Loading example.com mail settings...". The interface is built to simulate a standard webmail login portal. It prompts visitors to input account credentials into a password field. Once the user interacts with the form, any entered data is transmitted directly to the backend controlled by the threat actor.
Credential harvesting risks
Because the page features a password field designed to capture authentication details, visitors who type their credentials risk immediate account compromise. Attackers typically use harvested passwords to access personal email accounts, reset linked services, or launch further attacks. The presentation relies on deceptive loading elements to trick users into believing they are authenticating a legitimate mail service session.
Security vendor telemetry
urlscan classified the page as malicious, 9 of 92 VirusTotal engines flagged it on 17 Nov 2026, and OpenPhish blocks it, and PhishDestroy's evidence score for it is 75/100 (critical). Independent scanners and security feeds confirm the malicious nature of the deployment on vercel.app. Furthermore, still responded on 18 Nov 2026 at 10:37 UTC, indicating active availability on the network.
Source evidenceVirusTotal 9 / 924 sources
SourceResultRecorded · UTCOpen
VirusTotal
9 / 92 engine detections
Analysis:
Open report VirusTotalOriginal source recordObserved: 14 fields
This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.
Open report Title, description and generation record
The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
AI title
kope-two.vercel.app — Credential harvesting mail login page
AI description
kope-two.vercel.app presents a fake email login capturing account passwords, flagged by urlscan and 9 VirusTotal engines. Do not type sensitive data.
AI summary
Page layout and credential input The page hosted on kope-two.vercel.app presents a modal dialog centered over a grey background displaying standard documentation placeholder text in multiple languages, including English, Arabic, Chinese, French, Russian, and Spanish. A prominent blue email envelope icon sits above a loading bar and the text "Loading example.com mail settings...". The interface is built to simulate a standard webmail login portal. It prompts visitors to input account credentials into a password field. Once the user interacts with the form, any entered data is transmitted directly to the backend controlled by the threat actor. Credential harvesting risks Because the page features a password field designed to capture authentication details, visitors who type their credentials risk immediate account compromise. Attackers typically use harvested passwords to access personal email accounts, reset linked services, or launch further attacks. The presentation relies on deceptive loading elements to trick users into believing they are authenticating a legitimate mail service session. Security vendor telemetry urlscan classified the page as malicious, 9 of 92 VirusTotal engines flagged it on 17 Nov 2026, and OpenPhish blocks it, and PhishDestroy's evidence score for it is 75/100 (critical). Independent scanners and security feeds confirm the malicious nature of the deployment on vercel.app. Furthermore, still responded on 18 Nov 2026 at 10:37 UTC, indicating active availability on the network.
No, it is a fraudulent page hosted on vercel.app that collects passwords. It is flagged by urlscan and 9 VirusTotal engines.
What happens if I entered my password on kope-two.vercel.app?
The operators of the page receive your credentials instantly. You should change your password immediately on your real account and enable multi-factor authentication if available.
How can I report this malicious domain?
You can report kope-two.vercel.app to the hosting provider vercel.app to request immediate removal of the phishing content.
What we count Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Reachable · access restricted.
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.
Edge-IP reputation is not attributed to this domain.
Nameservers 4
ns1.vercel-dns-3.com
ns2.vercel-dns-3.com
ns3.vercel-dns-3.com
ns4.vercel-dns-3.com
Location describes the IP network.
TLS certificate
Issuer
WR1
Valid from
2026-10-31 11:46:10
Valid until
2027-01-29 11:46:09
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintb780bccea3104338b0f1dfb618d1613104d80c3ba127e19dc9307f2c9c56dfc4Certificate names · 1 SAN
*.vercel.app
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Observed timelinelast reachable: 2026-11-18 12:13 UTCcurrent episode first observed: 2026-11-19 00:08 UTCobserved RIP window: 2026-11-18 12:13 UTC → 2026-11-19 00:08 UTC · 11.92hmidpoint estimate ≈ 2026-11-18 18:10 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.
Technologies · 2 identified
V
Vercel
PaaS
Vercel is a cloud platform for static frontends and serverless functions.
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-18 09:39 UTC.
Recorded events: 10. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Hours from detection to the first unavailable observation: 14
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this observation.
ongoing
Recorded activity
3 entries
Lifecycle
Domain registered
VirusTotal analysis with detections+2485 d 8 h
Added to PhishDestroy+22 h 26 min
Added to PhishDestroy
kope-two.vercel.app
same minute
URLScan
Page captured
+22 h 26 min
VirusTotal
9/92 engine detections
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
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
Supporting signal — Shares a page feature, infrastructure or a collector label; not proof of one operator.
Discovery only — Same registrar or CDN edge: listed for navigation, not evidence of a link.
Each spoke is one reason a domain is linked to this report. Node size marks VirusTotal detections, dashed nodes are already offline, and the full lists follow below. Full list of related reports
Content matches4
Same favicon file hash, or a recorded page title that starts with the same 20 characters. A content match does not establish a shared phishing kit or owner.
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.
Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
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.
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Downloaded a file — do not open it and scan the device with security software
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed
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 kope-two.vercel.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
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 →
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.