VirusTotal
5 / 89 engine detections
レポートを開く“Firelight”
ブロックリスト掲載ドメイン: firelight.fi — コンテンツが利用できません. 証拠の概要: VirusTotal 5/89 (ChainPatrol, alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, VIPRE); 2 external…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
5 / 89 engine detections
レポートを開く4 community references
レポートを開くprovider verdict: clean
レポートを開く80/100
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
firelight.fi presented itself under the name "Firelight" and operated as a crypto wallet drainer targeting cryptocurrency holders. PhishDestroy first detected it on 2026-09-17. The site went offline the following day, 2026-09-18, and remained dead as of the last check on 2026-10-19. Despite its short active window, it was flagged across multiple independent threat-intelligence platforms before going dark.
Wallet drainers lure victims into connecting their crypto wallets through a convincing web interface, then prompt them to sign transactions or grant token approvals that hand control of their assets to the attacker. Once approval is granted, the drainer contract silently sweeps tokens and NFTs from the victim's wallet without any further interaction required. The victim typically loses all approved assets within seconds of signing, with no way to reverse the transfer.
Five of 89 engines on VirusTotal flagged firelight.fi on 2026-09-17, with detections from ChainPatrol, alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, and VIPRE. The domain also appears on four OTX threat-intelligence pulses. It was added to the blocklists maintained by PhishDestroy, MetaMask, and SEAL, meaning active wallet software would have warned users before they could interact with the site.
The domain was registered on 2026-04-25 through 101Domain GRS Ltd. and sat dormant for nearly five months before becoming active. It was hosted on Cloudflare's network, resolving to an IP geolocated to Canada, and used a Let's Encrypt TLS certificate issued under the YE2 authority, a common low-cost setup that lends a false appearance of legitimacy.
If you visited firelight.fi and connected your wallet, immediately revoke all token approvals granted during that session using a trusted approval-management tool, then transfer remaining assets to a fresh wallet address. If you signed any transaction, assume those assets are lost and report the incident to your wallet provider. Defenders and security teams should ensure firelight.fi is present in their blocklists and distribute the domain to any threat-feed subscribers; the MetaMask and SEAL blocklist entries mean most major wallet interfaces already block it.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
0x7bD6809f71a4CE08c4001baF8E89e3DB4E3C7fa6Format validated · Domain analysisIoC extraction recorded 2026-09-18 04:01:23 UTC
Last checked
Edge-IP の評判はこのドメインに起因しません。
ernest.ns.cloudflare.comkatelyn.ns.cloudflare.comLocation describes the IP network.
62b684ac87526387147125af2959697ae0931de9a6ae3f27f874ea329d99e687Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of firelight.fi · checked Sep 17, 2026
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.
firelight.fi
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
不明→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
到達可能→利用不可
到達可能
4 community references
View sourceNo threat flag
View source5/89 engine detections
View sourcefirelight.fi
View sourcePage captured
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
firelight.fi)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.