セキュリティレポートへ移動
ドメインのセキュリティと脅威インテリジェンス
wlive.plasmic.run favicon

wlive.plasmic.run

“Vercel Security Checkpoint”

レジストラ
Amazon
Resolved IP
216.150.1.65
Registered
2022年8月5日
PhishDestroy assessment クリティカル
可用性 最後に確認されたアクティブな状態 最新の保存された到達可能性の観測 観測された · HTTP probe
VirusTotal 検出数: 17/89 自動ブランドラベル:Ledger
2026年9月12日 CDN
API
このドメインは悪意のあるものとして報告されています
検出を報告するセキュリティ エンジン: 17。 細心の注意を払ってください — 資格情報や個人情報を入力しないでください。
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Domain age
レポート概要

Ledgerなりすまし: wlive.plasmic.run — 最後に確認されたアクティブな状態 (HTTP 308). 証拠の概要: VirusTotal 17/89 (BitDefender, Chong Lua Dao, CRDF, CyRadar, ESET); URLScan malicious…

元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。

Source evidenceVirusTotal 17 / 89 5 sources

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

ネットワークセキュリティインテリジェンス
CF Cloudflare Radar Verdict 悪意あり
Phishing

Analysis

クリティカル
VirusTotal
17 / 89
Page captures
3

PhishDestroy threat report

Overview

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.

How the scam works

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.

Evidence

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.

Infrastructure

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.

What to do

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.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

保存済みキャプチャ · 3 captures

Observed page title
Vercel Security Checkpoint
Automated brand references
Ledger
TLS証明書
発行者 Let's Encrypt / YR1

Domain details

ドメイン
URLScan verdict 悪意あり score 100 Phishing brand: Ledger report ↗
IP Context Vercel shared edge origin IP hidden Edge-IP の評判はこのドメインに起因しません。
Registrar (base domain) Amazon US(US)
不正利用連絡先abuse@vercel.com
ICANNレジストリICANN Lookup (RDAP) →
Registration (base domain)plasmic.run · 作成日 2022年8月5日 — Expires 2027年8月5日
HTTPステータス308 Permanent Redirect
技術詳細Provenance & timestamps
初確認2026年9月12日
DOM Analysisanalyzed 2026年9月12日score 88/1001 brand signal
Submitted URLhttps://wlive.plasmic.run/
Favicon Hash
ICANN OVERSIGHT Registration: plasmic.run

認定と RAA の背景

Registrar accreditation and DNS abuse obligations

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.

Accreditation is a contract, not a safety certification.

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.

Accountability draft 自動送信は一切行われません。

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
216.150.1.65
Network ASN
AS16509
Organization
Amazon.com, Inc.
Observed location
Walnut, US
Server header
Vercel

Edge-IP の評判はこのドメインに起因しません。

Location describes the IP network.

TLS証明書

Issuer
Let's Encrypt / YR1
Valid from
2026-07-14 13:13:23
Valid until
2026-10-12 13:13:22
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-09-12 13:02:03 UTC
Collection source
PhishDestroy collector
Certificate fingerprintec8e362847a5ecbb00ffaebc10be1eb8492cbf61cc41bffeec027bb8c775c772
Certificate names · 1 SANs
  • plasmic.run

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-19 22:15:59 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-19 22:15:59 UTC
RDAP registration 不明
Observed timeline last reachable: 2026-10-19 22:15:59 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
使用技術 · 1 identified
Detected via Cloudflare Radar · Wappalyzer engine
このドメインを報告する 証拠を提出し、他の人を守る手助けをしましょう

VirusTotalによる分析

17 / 89 セキュリティ ベンダーがこのドメインにフラグを立てました
View on VT
Last analyzed First positive detection Previous stored snapshot: 7 detections
BitDefender
Chong Lua Dao
CRDF
CyRadar
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
カスペルスキー
LevelBlue
Lionic
ネットクラフト
SOCRadar
ソフォス
VIPRE
Webroot
サイトパフォーマンス分析

Google PageSpeed Insights — mobile performance audit of wlive.plasmic.run · checked Sep 12, 2026

50
Needs Work
Performance
FCP
2.86s
First Contentful Paint
LCP
5.91s
Largest Contentful Paint
CLS
0.614
Cumulative Layout Shift
TBT
2ms
Total Blocking Time
SI
3.53s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

wlive.plasmic.run
保存済みの結果
Cloaked / Filtered
Stored observation history18

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  2. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  3. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  4. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  5. Availability monitor · Recorded state

    不明→redirected

    http_redirect

Earlier observations 13
  1. Availability monitor · Recorded state

    redirected→protected

    http_access_restricted · access_restriction

  2. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  3. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  4. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  5. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  6. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  7. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  8. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  9. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  10. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  11. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  12. Availability monitor · Recorded state

    不明→redirected

    http_redirect

  13. Availability monitor · First collection record

    到達可能

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    17/89 engine detections

    View source
  3. Added to PhishDestroy

    wlive.plasmic.run

    View source
  4. URLScan

    Page captured

    View source

類似ドメイン

保存された類似ドメイン:151 件

すべて表示(88)
eldger.com transposition kedger.com replacement kledger.com insertion l3dger.com replacement ldeger.com transposition ldger.com omission le.dger.com subdomain lecger.com replacement ledber.com replacement ledegr.com transposition leder.com omission ledg3r.com replacement ledge.com omission ledged.com replacement ledgedr.com insertion ledgee.com replacement ledgeer.com repetition ledgercom.com various ledget.com replacement ledgewr.com insertion ledgger.com repetition ledgir.com vowel-swap ledgor.com vowel-swap ledgr.com omission ledgre.com transposition ledgrer.com insertion ledgsr.com replacement ledgwer.com insertion ledgwr.com replacement ledher.com replacement ledhger.com insertion ledsger.com insertion ledtger.com insertion ledyer.com replacement ledzer.com replacement leedger.com insertion legder.com transposition leger.com omission lerdger.com insertion lerger.com replacement lesger.com replacement lewdger.com insertion lidger.com vowel-swap lledger.com repetition lodger.com vowel-swap lrdger.com replacement lsdger.com replacement oedger.com replacement pedger.com replacement pledger.com insertion dedger.com bitsquatting hedger.com bitsquatting iedger.com homoglyph l-edger.com hyphenation ladger.com bitsquatting lcdlger.com homoglyph lddger.com bitsquatting lebger.com homoglyph leclger.com homoglyph ledcer.com bitsquatting leddger.com insertion ledeer.com bitsquatting ledeger.com insertion ledfer.com bitsquatting ledg-er.com hyphenation ledgar.com bitsquatting ledger0.com addition ledger1.com addition ledger4.com addition ledger5.com addition ledger6.com addition ledgerb.com addition ledgerc.com addition ledgerf.com addition ledgeri.com addition ledgern.com addition ledgerq.com addition ledgerx.com addition ledges.com bitsquatting ledgez.com bitsquatting ledgur.com bitsquatting lediger.com homoglyph ledqer.com homoglyph leeger.com bitsquatting leelger.com homoglyph lefger.com bitsquatting letger.com bitsquatting ludger.com bitsquatting

151 件中 100 件を表示

証拠および外部報告書

詳細な分析
Help & reporting

このサイトによって何か影響を受けましたか?

3 evidence signal groups linked 0 stored notification records 最後に確認されたアクティブな状態

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。

Official reporting routes

復旧を装った詐欺に注意! 犯罪者は、捜査員、弁護士、または回収業者を装い、被害者に再び連絡を取る可能性があります。 前払い料金を支払ったり、資格情報を共有したりしないでください。 回復詐欺について詳しくはこちら →

お住まいの地域の当局へ報告してください

サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。

97か国のディレクトリ

Template-based draft · optional AI wording assistance requires separate consent

AI 支援ドラフト — インシデントの詳細は AI プロバイダーによって処理されます · 自分で確認して送信する
After a phishing incident

被害者への推奨事項とアドバイス

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.

  • すべてのパスワードを変更する — メール、Exchangeアカウントなど、同じパスワードを使用しているものすべて
  • 2段階認証を有効にする 認証アプリ(SMSではない)を使用する。SMSによる復旧機能を無効にする
  • カードの凍結 フィッシングサイトに銀行口座情報を入力してしまった場合

レポート作成のために、どのような情報を収集すべきでしょうか?

FBIのガイドライン

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • 正確な日時 — 各取引および詐欺師との最初の接触について
  • スクリーンショット — 詐欺サイト、チャットメッセージ、メール、ウォレットでの取引、ソーシャルメディア
  • すべてのURLおよびドメイン 詐欺師が使用した(以下を含む) wlive.plasmic.run)
  • コミュニケーション — 詐欺師が使用したメール、テキストメッセージ、電話番号、ユーザー名

たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。

この詐欺はどこに通報すればいいですか?

  • FBI IC3 — インターネット犯罪通報センター(米国連邦政府の通報窓口)
  • ユーロポール — 欧州におけるサイバー犯罪の報告(EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • 地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • 偽のウェブサイト — 正規サイトのドメインをわずかに変更した、ピクセル単位で完璧に再現されたクローンサイト
  • pig butchering — TelegramやWhatsApp、出会い系アプリを通じて数週間にわたって信頼関係を築き、その後、金銭をだまし取られる
  • 詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AIを利用した詐欺 — ディープフェイク、自動化されたフィッシング、AI生成サイトにより、詐欺の発見が難しくなっている

今後、どうすれば身を守ることができるでしょうか?

  • 公式サイトをブックマークする — メール、DM、広告に含まれるリンクは絶対にクリックしないでください
  • ドメインの確認 — 確認する PhishDestroy 操作を行う前に、HTTPS、スペル、ドメインの登録期間を確認してください。
  • 「良すぎて怪しい」=詐欺 — 確実なリターン、有名人の推薦、差し迫った締め切り

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

最新情報を入手し、安全を確保しましょう

リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください

リアルタイム脅威情報フィード この掲載情報について異議を申し立てる
About this reportSources, observation dates and corrections

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

このレポートを埋め込む

この脅威情報を、ご自身のウェブサイトやブログで共有してください

embed.html
<iframe
  src="https://phishdestroy.io/ja/embed/domain/wlive.plasmic.run"
  title="PhishDestroy threat report for wlive.plasmic.run"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>