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@colocrossing.com.
The latest stored availability evidence still shows the domain reachable; 13 days 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.
xfinity.eventivite.link is a credential phishing page built to look like the Xfinity account login, served under the title "Sign in | Xfinity". It targets Xfinity customers who can be persuaded to sign in from a link rather than through Xfinity's own app or site. The parent domain eventivite.link has no connection to Xfinity, and the brand name is placed in front of it only to make the address look legitimate at a glance. PhishDestroy first saw it on 2026-10-07. On 2026-10-19 the site was still responding, but its DNS was inactive for the phishing content.
How the scam works
Victims usually arrive through an email or text claiming a billing problem, a service change or an account alert, with a link to "sign in". The page copies the Xfinity login screen, so anything typed into it goes straight to the operators. A stolen Xfinity login can expose billing and payment details and personal information. It can also open the linked email account, which criminals can use to reset passwords on other services or to send further phishing from a trusted address.
Evidence
Ten of 92 VirusTotal engines flagged the domain on 2026-10-07, including Google Safe Browsing, Netcraft, Fortinet, Sophos, Forcepoint ThreatSeeker, Emsisoft, G-Data and SOCRadar. Several independent vendors reaching the same conclusion within days of the domain's creation is a strong signal. Google Safe Browsing classes it as social engineering, which triggers warnings in most major browsers. urlscan.io rated the page malicious and detected the Xfinity brand on it, and PhishDestroy lists it on its blocklist.
Infrastructure
The domain was registered on 2026-10-05 through Cloudflare, Inc. and was being detected two days later. That short gap is typical of throwaway phishing domains set up for a single campaign. It was hosted in the United States on the ColoCrossing network, part of HostPapa. A free Let's Encrypt certificate gave it a padlock, which shows only that the connection was encrypted, not that the site is genuine.
What to do
If you entered your Xfinity username and password here, change that password immediately from Xfinity's official app or by typing the address yourself. Then change it anywhere else you reused it, and turn on two-step verification. Review the account for changed contact details, new authorized users or payment changes, and check any email account tied to it for unfamiliar forwarding rules or sign-ins. Watch your card statements if payment details were shown or entered. Defenders should block the domain and the parent eventivite.link at mail and web gateways, and search logs for users who visited or submitted forms.
For the registrable domain eventivite.link 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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-19 22:39:26 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-07 12:19:24 UTCcurrent episode first observed: 2026-10-08 20:20:32 UTCobserved RIP window: 2026-10-07 12:19:24 UTC → 2026-10-08 20:20:32 UTC · 32.02hmidpoint estimate ≈ 2026-10-08 04:19:58 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.
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.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
(US)
