VirusTotal
6 / 89 engine detections
Mở báo cáo“Flying Tulip”
Lừa đảo: flyingtulip.pro — Nội dung không có sẵn. Tóm tắt bằng chứng: VirusTotal 6/89 (alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar)…
Phân tích chi tiết của PhishDestroy AI bên dưới được giữ bằng tiếng Anh để bảo toàn hồ sơ pháp chứng gốc.
6 / 89 engine detections
Mở báo cáochecked — no detections recorded
Mở báo cáo3 community references
Mở báo cáoprovider verdict: clean
Mở báo cáoNo threat flag
Mở báo cáoNo malicious flag
Mở báo cáoResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
flyingtulip.pro is a phishing site that presented itself under the page title "Flying Tulip," borrowing the name of the crypto project to win the trust of its community and wallet users. PhishDestroy first flagged it on 2026-09-19. The site went offline on 2026-09-23, and its DNS was still inactive when last checked on 2026-10-19. The domain could return under new hosting, so it should stay blocked.
Impersonation pages like this copy the look and name of a real project so visitors believe they are on an official site. These pages usually promise a token sale, airdrop or reward, then push the visitor to connect a wallet, sign a transaction or type in a recovery phrase. A signed approval or a leaked seed phrase lets the operators move tokens out of the wallet, and those transfers cannot be reversed. The "Flying Tulip" title shows the brand the site relied on to look legitimate.
MetaMask and SEAL list the domain on their blocklists alongside PhishDestroy. MetaMask's listing matters most for victims, because the wallet can warn users before they connect. On 2026-09-21, 6 of 89 VirusTotal engines flagged the site: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar and VIPRE. That is a modest share of engines, but it is typical for a short-lived crypto lure. The domain also appears in 3 AlienVault OTX threat pulses, so other researchers tracked it independently.
The domain was registered through NameSilo, LLC on 2026-06-21, about three months before PhishDestroy detected it. That gap suggests the domain was held in reserve before the campaign went live. The site sat behind Cloudflare's network, with an address geolocated to Canada, which hides where the real server was. Its certificate came from Google Trust Services (WE1), so the padlock in the browser only meant the connection was encrypted, not that the site was genuine.
If you connected a wallet to flyingtulip.pro, check your token approvals with a revocation tool and revoke anything you do not recognize. If you entered a seed phrase or private key, treat that wallet as compromised. Move any remaining funds to a new wallet created with a fresh phrase. Only reach Flying Tulip through links from its verified official channels. Security teams should block the domain at DNS and proxy level and watch for lookalike registrations reusing the Flying Tulip name.
Last checked
Danh tiếng của Edge-IP không được quy cho tên miền này.
cameron.ns.cloudflare.compearl.ns.cloudflare.comsmtp.google.compriority 1Location describes the IP network.
a3d7e7bb28f693c73834af27a79664ec80da44d6e1fcfac970687d2c9b137d86Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
flyingtulip.pro
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Không rõ→dns_inactive
dns_nxdomain
Không rõ→dns_inactive
dns_nxdomain
Không rõ→dns_inactive
dns_nxdomain
Không rõ→dns_inactive
dns_nxdomain
Không rõ→dns_inactive
dns_nxdomain
Không rõ→dns_inactive
dns_nxdomain
Không rõ→dns_inactive
dns_nxdomain
Không rõ→dns_inactive
dns_nxdomain
Không rõ→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
Có thể truy cập→Không có sẵn
0→2
No threat flag
View source6/89 engine detections
View source3 community references
View sourcePD-20260919-AC6476
Page captured
View sourceflyingtulip.pro
View sourcePD-20260919-AC6476 Recipient: abuse@identitydigital.com Nếu bạn đã nhập thông tin xác thực tài khoản, thông tin cá nhân hoặc thông tin thanh toán hoặc đã tải xuống tệp từ miền này, hãy hành động ngay lập tức. Dưới đây là các nguồn lực giúp bạn báo cáo vụ việc và bảo vệ chính mình.
Chọn quốc gia của bạn để nhận liên hệ tội phạm mạng chính thức hoặc soạn thảo đơn khiếu nại →.
Template-based draft · optional AI wording assistance requires separate consent
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.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
flyingtulip.pro)Dù bạn chưa nắm rõ tất cả các chi tiết — vẫn nên nộp báo cáo. Ngay cả những thông tin không đầy đủ cũng vẫn có ích cho công tác điều tra.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Phân tích mối đe dọa bằng cách sử dụng danh sách chặn được lưu trữ, WHOIS, DNS và bằng chứng quét công khai
Quét ngayHãy gửi các tên miền đáng ngờ đến cơ sở dữ liệu mối đe dọa của chúng tôi — để bảo vệ cộng đồng
Báo cáoCác báo cáo lừa đảo gần đây và những thay đổi về tính khả dụng được quan sát thấy
Theo dõiTheo dõi các mối đe dọa đang diễn ra hoặc phản đối danh sách này nếu bạn cho rằng đây là kết quả báo động sai
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.