VirusTotal
3 / 92
engines flag the domain · 2 suspicious
“Contributions Ledger | 独立した研究シリーズ”
3 / 92
engines flag the domain · 2 suspicious
No threat flag
Not on Google threat lists at check time
0
threat pulses mention the domain
Online · HTTP 200
Cloudflare · 188.114.97.1 · TLS: Google Trust Services
malicioussuspicious
Each check shows its own collection time. Zero detections do not guarantee safety.
Ledgerなりすまし: contributions-ledger.org — 最後に確認されたアクティブな状態 (HTTP 200). 証拠の概要: VirusTotal 9/92 (alphaMountain.ai, BitDefender, CRDF, Forcepoint ThreatSeeker…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
9 / 92 engine detections
レポートを開くSuspicious
レポートを開く2 community references
レポートを開く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
contributions-ledger.org is an impersonation phishing page that trades on the Ledger name to reach owners of Ledger hardware wallets. PhishDestroy first flagged it on 2026-10-09, three days after the domain was registered. As of 2026-10-19 the site was still online and serving content, so it remains a live risk.
The page title reads "Contributions Ledger | 独立した研究シリーズ", Japanese for "independent research series", which presents the site as a research project, while we classify it as Ledger impersonation. Ledger-themed phishing typically borrows the brand's credibility to push visitors toward a fake support, update or verification step. That step asks for the 24-word recovery phrase or a wallet connection. Anyone who hands over the phrase gives the attacker full control of every account derived from that device, and the funds can be swept within minutes.
Nine of 92 VirusTotal engines flagged the domain as of 2026-10-13. They include Kaspersky, BitDefender, G-Data, Forcepoint ThreatSeeker, alphaMountain.ai, CRDF, Gridinsoft and SOCRadar. That is a minority of engines, but it spans established antivirus vendors and threat-intel feeds. The domain is also listed by MetaMask and the SEAL security alliance alongside PhishDestroy, and it appears in two AlienVault OTX threat pulses. Because wallet-side blocklists are on board, many MetaMask users should see a warning before the page loads.
The domain was registered through Cloudflare, Inc. on 2026-10-06 and drew detection within three days. That short gap fits a freshly stood-up campaign domain rather than a long-running site. It resolves to Cloudflare's network, with the address geolocated to Canada. This means the origin server sits behind Cloudflare's proxy and is not directly exposed.
Never type a Ledger recovery phrase into any website, because Ledger does not ask for it online. If you entered your phrase here, treat the wallet as compromised. Move remaining funds to a newly initialized device with a fresh phrase, and do not reuse the old one. If you connected a wallet or signed anything, revoke token approvals with a reputable approval checker and watch for unexpected transactions. Defenders should block the domain at DNS and proxy level and send abuse reports to Cloudflare as registrar and host.
Last checked
Edge-IP の評判はこのドメインに起因しません。
monroe.ns.cloudflare.comowen.ns.cloudflare.comLocation describes the IP network.
7fb21cdcdf7cba9a1adbbc31ad29f06c0bdac18d19fbec3170267b6639130d8cSaved 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 contributions-ledger.org · checked Oct 9, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
到達可能
No threat flag
View source9/92 engine detections
View source2 community references
View sourcecontributions-ledger.org
View sourcePage captured
View source保存された類似ドメイン:151 件
151 件中 100 件を表示
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
contributions-ledger.org
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 ↗
contributions-ledger.org)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.