lilac-haven.com is an impersonation phishing site. It dresses itself up as a service people already trust so that visitors lower their guard and act on what the page asks. PhishDestroy first flagged it on 2026-09-18. As of 2026-10-19 the site is still online and serving its content, so it remains a live risk to anyone who lands on it.
How the scam works
Impersonation pages copy the look, wording and flow of a legitimate brand, then insert a step that benefits the operator. That step is usually a login form, a verification request, a payment or a request for identity details. Whatever the visitor types goes straight to the people running the site. The victim can lose account access, card or bank details, or personal information that is later reused for fraud and further targeted phishing. The name lilac-haven.com has no obvious tie to any real brand, which is common for throwaway domains that get their credibility from the page design rather than the address.
Evidence
On 2026-09-29, 14 of 91 VirusTotal engines classed the domain as malicious. Those engines included BitDefender, ESET, Fortinet, G-Data, Forcepoint ThreatSeeker, Gridinsoft, alphaMountain.ai and the Vietnamese anti-scam group Chong Lua Dao. Detection by vendors who run independent feeds carries more weight than a single verdict. The domain also appears in 4 AlienVault OTX threat pulses, so other researchers have tracked it as well. Most engines still show it as clean, which means many browsers and filters may not warn users yet.
Infrastructure
The domain was registered through Dynadot Inc on 2025-11-10, roughly ten months before PhishDestroy detected it. That long gap suggests it was either held in reserve or reused for this campaign. Traffic runs through Cloudflare, with the edge address resolving to Canada, so the real origin server stays hidden behind the proxy. Its certificate comes from Google Trust Services. The padlock in the browser shows only that the connection is encrypted, not that the site is genuine.
What to do
If you entered a password on lilac-haven.com, change it right away on the real service and on any other account that shares it, then turn on two-factor authentication. If you submitted card or bank details, call your bank to block the card and dispute any charges. If you shared identity documents or personal details, watch for follow-up phishing that uses them to seem convincing. Defenders should block the domain at DNS and web proxies, add it to mail filtering, and report it to Cloudflare and Dynadot to speed up takedown.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation활성 콘텐츠Ordinary HTTP content served90%2026-10-19 10:35:23 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-19 10:35:23 UTClast content: 2026-10-19 10:35:23 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.
기술 · 5 identified
N
Node.js
Programming languages
Node.js is an open-source, cross-platform, JavaScript runtime environment that executes JavaScript code outside a web browser.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Template-based draft · optional AI wording assistance requires separate consent
AI 지원 초안 - 사고 세부정보는 AI 제공업체에서 처리됩니다. · 직접 검토하고 제출하세요.
After a phishing incident
피해자를 위한 권고 사항 및 조언
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
지금 당장 어떻게 해야 할까요?
긴급
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
모든 비밀번호 변경 — 이메일, 익스체인지 계정 등, 동일한 비밀번호를 사용하는 모든 것
2단계 인증 활성화 인증 앱(SMS 제외)을 사용합니다. SMS 기반 복구 기능을 비활성화하세요.
카드 동결 피싱 사이트에 은행 계좌 정보를 입력한 경우
보고서를 작성하기 위해 어떤 정보를 수집해야 할까요?
FBI 지침
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.
정확한 날짜 및 시간 — 각 거래 내역 및 사기범과의 첫 접촉 시점
스크린샷 — 사기 웹사이트, 채팅 메시지, 이메일, 지갑 거래, 소셜 미디어
모든 URL 및 도메인 사기꾼이 사용한 (다음과 같은 것들을 포함하여 lilac-haven.com)
커뮤니케이션 — 사기꾼이 사용한 이메일, 문자, 전화번호, 사용자 이름
비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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.
How do phishing scams typically work?
가짜 웹사이트 — 도메인을 약간만 변경한, 정식 사이트와 픽셀 단위로 완벽하게 일치하는 복제 사이트
pig butchering — Telegram·왓츠앱·데이트 앱을 통해 몇 주에 걸쳐 신뢰를 쌓은 뒤, 돈을 훔쳐갔다
회복 사기 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI를 이용한 사기 — 딥페이크, 자동화된 피싱, AI로 생성된 사이트 등으로 인해 사기 행각을 적발하기가 더 어려워지고 있다
앞으로 어떻게 하면 스스로를 지킬 수 있을까요?
공식 사이트 즐겨찾기 추가 — 이메일, DM 또는 광고에 포함된 링크는 절대 클릭하지 마세요
도메인 확인 — 확인하기 PhishDestroy 상호작용을 시작하기 전에 HTTPS, 맞춤법, 도메인 등록 기간을 확인하세요.
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)
