VirusTotal
14 / 91 engine detections
レポートを開く“SOURCE”
MetaMaskなりすまし: czsource.com — コンテンツが利用できません. 証拠の概要: VirusTotal 14/91 (alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker); Google Safe…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
14 / 91 engine detections
レポートを開くThreat flag recorded
レポートを開く1 community reference
レポートを開くprovider verdict: clean
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
czsource.com hosted an impersonation phishing page whose browser title read simply "SOURCE". It was built to pass itself off as a legitimate crypto service and lure wallet users into trusting it. PhishDestroy first saw it on 2026-09-15. The site has been offline since 2026-09-28 and was still dead when last checked on 2026-10-19.
Impersonation pages copy the name, look and wording of a real project so that a visitor arriving from a search ad, social post or direct message believes they are on the genuine site. The bare "SOURCE" title fits that pattern: a short, official-looking brand label with no indication that the operator is unrelated to the real project. From there, the page asks for whatever the attackers can monetize. That can be login credentials, a recovery phrase, or a wallet connection followed by a transaction or approval that hands over funds. Anything submitted or signed on such a page should be treated as compromised.
Fourteen of 91 VirusTotal engines flagged the domain as of 2026-09-25. The flagging vendors include Google Safe Browsing, BitDefender, ESET, Fortinet, Forcepoint ThreatSeeker, G-Data, CRDF and alphaMountain.ai, a spread of independent vendors rather than one outlier. Google Safe Browsing classifies it as SOCIAL_ENGINEERING, which is the category browsers use for deceptive pages. The wallet-security ecosystem also caught it: MetaMask and SEAL both list it alongside PhishDestroy, and it appears in one AlienVault OTX pulse.
The domain was registered through Cloudflare, Inc. on 2026-02-15, about seven months before PhishDestroy detected it. That gap suggests it was either held in reserve or ran quietly before drawing attention. It sat behind Cloudflare's network with a Canadian-located edge address, so the IP reveals nothing about the real origin server. The Google Trust Services certificate only means the padlock appeared as usual. It says nothing about whether the site was safe.
If you entered a recovery phrase on czsource.com, assume the wallet is lost to the attackers and move any remaining assets to a new wallet created with a fresh phrase. If you connected a wallet and signed anything, review and revoke token approvals for the addresses you used. If you typed a password, change it everywhere it was reused and turn on app-based 2FA. Defenders should block the domain, search mail and proxy logs for visits between 2026-09-15 and 2026-09-28, and alert any users who reached it.
Last checked
Edge-IP の評判はこのドメインに起因しません。
betty.ns.cloudflare.comrazvan.ns.cloudflare.comLocation describes the IP network.
24d1f420d81a25bf0b31998ce2fe4b9ddd3d3d9948193beaf784733d0f63f407Saved 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 czsource.com · checked Sep 15, 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.
czsource.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
到達可能→利用不可
No flag recorded→Flag recorded
到達可能
Threat flag recorded
View source14/91 engine detections
View sourcePage captured
View source1 community references
View sourceczsource.com
View source保存された類似ドメイン:79 件
Listed 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 ↗
czsource.com)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.