VirusTotal
17 / 89 engine detections
レポートを開く“Vercel Security Checkpoint”
Ledgerなりすまし: wlive.plasmic.run — 最後に確認されたアクティブな状態 (HTTP 308). 証拠の概要: VirusTotal 17/89 (BitDefender, Chong Lua Dao, CRDF, CyRadar, ESET); URLScan malicious…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
17 / 89 engine detections
レポートを開く悪意あり
レポートを開く悪意あり
レポートを開くno community references
レポートを開くNo threat flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
wlive.plasmic.run is a phishing page that impersonates Ledger, the hardware wallet maker, and targets people who keep crypto on a Ledger device. PhishDestroy first flagged it on 2026-09-12. As of 2026-10-19 the site was still online and answering with a redirect, so it can still send visitors on to its next stage. Its page title reads "Vercel Security Checkpoint", while we classify the site as Ledger impersonation.
Fake Ledger pages usually invent an urgent problem, such as a security alert, a required firmware update or a wallet that needs to be "verified" or "resynchronized". The victim is then asked to type in the 24-word recovery phrase or connect their wallet. A checkpoint-style title like this one makes the page look like a routine security step before the real request appears. Anyone who enters their recovery phrase gives the attacker full control of the wallet, and the funds can be moved out within minutes. Ledger never asks for a recovery phrase on a website, in an app or by message.
On 2026-09-20, 17 of 89 VirusTotal engines flagged the site. They include BitDefender, ESET, Fortinet, Emsisoft, Forcepoint ThreatSeeker, CRDF, CyRadar and the Vietnamese anti-scam group Chong Lua Dao. That is a solid spread of independent security vendors agreeing that the site is malicious. urlscan.io also returned a malicious verdict and recognized Ledger branding on the page, which supports the impersonation finding.
The page runs on a subdomain of plasmic.run, a parent domain registered on 2022-08-05 through Amazon Registrar, Inc. That registration date is years before this page appeared, so its age does not make the site trustworthy. Traffic is served from 216.150.1.65 on Amazon's AS16509 network in the United States, and the site uses a free Let's Encrypt certificate. The padlock in the browser only means the connection is encrypted. It says nothing about who runs the page.
If you typed your Ledger recovery phrase into this site, treat the wallet as compromised. Set up a new wallet with a fresh phrase, ideally after resetting your device, and move any remaining funds there immediately. Never reuse the old phrase. If you connected a wallet or signed anything, check for unfamiliar token approvals and revoke them. Security teams should block the hostname and its redirect targets, and should warn users that Ledger support will never ask for a seed phrase.
For the registrable domain plasmic.run behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
ec8e362847a5ecbb00ffaebc10be1eb8492cbf61cc41bffeec027bb8c775c772plasmic.runSaved 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 wlive.plasmic.run · checked Sep 12, 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.
wlive.plasmic.run
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
redirected→protected
http_access_restricted · access_restriction
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
不明→redirected
http_redirect
到達可能
No threat flag
View source17/89 engine detections
View sourcewlive.plasmic.run
View sourcePage captured
View source保存された類似ドメイン:151 件
151 件中 100 件を表示
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 ↗
wlive.plasmic.run)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.