VirusTotal
4 / 89 engine detections
보고서 열기“Film Ledger”
beastmarkart.github.io — 콘텐츠를 사용할 수 없음 (HTTP 404). 브랜드 사칭: Ledger; 사기 유형: Impersonation. 증거 요약: VirusTotal 4/89 (ESET, G-Data, Gridinsoft, Sophos); URLScan malicious verdict; PhishDestroy score 65/100. 등록기관: MarkMonitor.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
4 / 89 engine detections
보고서 열기악성
보고서 열기no community references
보고서 열기provider verdict: clean
보고서 열기No threat flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
AI-assisted evidence review
beastmarkart.github.io is a phishing page that impersonated Ledger, the hardware wallet maker, to target people who keep crypto on Ledger devices. It sat on a GitHub Pages project subdomain, so the address borrowed GitHub's name rather than a lookalike of Ledger's own. PhishDestroy first flagged it on 2026-09-11, and it went offline that same day. When checked again on 2026-10-19, the root returned no content.
The page carried the title "Film Ledger." That title reads more like a film or media project than wallet software, while the content and urlscan.io's brand detection led us to classify it as Ledger impersonation. Ledger phishing pages usually pose as a firmware update, a security alert or a Ledger Live sync step. They then ask the visitor to type in the 24-word recovery phrase. Anyone who enters that phrase hands over full control of every account derived from it, and the attacker can empty the wallet from any device without touching the hardware.
urlscan.io rated the page malicious and recognised Ledger branding on it. On VirusTotal, 4 of 89 engines flagged it on 2026-09-11: ESET, G-Data, Gridinsoft and Sophos. That is a modest count, which is common for short-lived pages on shared hosting, but it comes from several independent vendors and matches the urlscan.io result. PhishDestroy lists the domain on its own blocklist.
The 2013-03-08 registration date and the MarkMonitor registrar belong to github.io itself, which GitHub owns. They say nothing about when this operator set up the page. Traffic resolved to Fastly in the US, the content delivery network behind GitHub Pages. Free project hosting like this lets a phishing page go live within minutes under a trusted parent domain, and that is why the subdomain, not the registration date, is the relevant indicator.
If you typed your Ledger recovery phrase into this page, treat the wallet as compromised. Set up a new device or reset your current one with a freshly generated phrase, and move any remaining funds there immediately. Ledger never asks for your recovery phrase on a website, by email or in chat, so any request for it is a scam. Defenders should block the beastmarkart.github.io subdomain without blocking all of github.io. They should also watch for other GitHub Pages sites using Ledger branding and report new ones to GitHub for removal.
urlscan.io scan and screenshot: https://urlscan.io/result/01a08b67-97ff-775d-b3f7-328dfbedaee1/
VirusTotal report: https://www.virustotal.com/gui/domain/beastmarkart.github.io
Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=beastmarkart.github.io
Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/
Site owner? Request a review: https://phishdestroy.io/appeals/
Edge-IP 평판은 이 도메인에 귀속되지 않습니다.
Location describes the IP network.
Saved 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 beastmarkart.github.io · checked Sep 11, 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.
http_other: raw=http_404; http=404; via=http_proxy; server=GitHub.com
beastmarkart.github.io
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
알 수 없음→inactive
http_no_content
알 수 없음→inactive
http_no_content
알 수 없음→inactive
http_no_content
알 수 없음→inactive
http_no_content
알 수 없음→inactive
http_no_content
알 수 없음→inactive
hosting_placeholder · placeholder_page
알 수 없음→inactive
hosting_placeholder · placeholder_page
알 수 없음→inactive
hosting_placeholder · placeholder_page
접속 가능→이용 불가
No threat flag
View source4/89 engine detections
View sourcebeastmarkart.github.io
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 ↗
beastmarkart.github.io)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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
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.