보안 보고서로 이동
도메인 보안 및 위협 인텔리전스
trezoio-started.blogspot.si favicon

trezoio-started.blogspot.si

“https://trezoio-started.blogspot.si/”

등록기관
MarkMonitor
Resolved IP
142.250.154.132
Registered
2007년 7월 23일
PhishDestroy assessment 심각
가용성 마지막으로 알려진 활성 최근에 저장된 도달 가능성 관찰 관측됨 · HTTP probe
VirusTotal 탐지: 10/89 Automated brand label: Google
2026년 9월 1일
API
이 도메인은 악성 도메인으로 표시되었습니다.
탐지를 보고하는 보안 엔진: 10. 극도의 주의를 기울이십시오 — 자격 증명이나 개인 정보를 입력하지 마십시오.
VirusTotal
engine detections
Google Safe Browsing
Domain age
보고서 요약

trezoio-started.blogspot.si — 마지막으로 알려진 활성 (HTTP 302). 브랜드 사칭: Google; 사기 유형: Impersonation. 증거 요약: VirusTotal 10/89 (alphaMountain.ai, BitDefender, Chong Lua Dao, ESET, Emsisoft); CF Radar malicious; PhishDestroy score 90/100. 등록기관: MarkMonitor.

원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.

Source evidenceVirusTotal 10 / 89 4 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
10 / 89

AI-assisted evidence review

Overview

trezoio-started.blogspot.si is an impersonation phishing page built on Google's free Blogger platform. Its name echoes Trezor's official "start" onboarding page, so it targets people who have just bought a Trezor hardware wallet and are searching for setup instructions. PhishDestroy first flagged it on 2026-09-01. As of 2026-10-19 the site was still online and redirecting visitors onward.

How the scam works

Fake Trezor setup pages copy the look of the real onboarding process and then push the visitor toward a step the genuine process never includes. That step is usually typing the 12- or 24-word recovery phrase into a web form, or downloading a counterfeit wallet app that collects the phrase later. Anyone holding that phrase controls every coin the wallet protects and can empty it from any device, with no way to reverse the transfers. The page title shows nothing but the site's own address, which gives no hint of the content behind the redirect.

Evidence

On 2026-09-13, 10 of 89 VirusTotal engines flagged the address. The vendors included alphaMountain.ai, BitDefender, Chong Lua Dao, ESET, Emsisoft, Lionic, Netcraft and PhishFort. Several of these, notably PhishFort, Netcraft and Chong Lua Dao, specialise in phishing and crypto fraud, so their agreement carries weight even though most engines stayed silent. Among blocklists, it appears on PhishDestroy's.

Infrastructure

The 2007-07-23 registration date and the MarkMonitor registrar belong to Google's blogspot.si domain, not to the scammer. The operator only had to create a free blog subdomain, which takes minutes and costs nothing. Hosting sits on Google LLC's network in the US, and the certificate comes from Google Trust Services. The padlock and the Google infrastructure therefore say nothing about who runs the page.

What to do

Trezor never asks for your recovery phrase on a website or blog. If you typed it here, assume it is compromised. Set up a genuine device with a new seed and move your funds there immediately, before anything else. If you installed software from this page, uninstall it, run a malware scan, and get Trezor Suite only through Trezor's official site. Security teams should block the subdomain, report it to Google's Blogger abuse channel, and warn users that hardware-wallet setup guides on free blog hosts are a common lure.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Domain details

도메인
IP 평판 abuse score 0/100 23 reports Port ScanHackingBrute-ForceExploited HostSSH checked 2026년 10월 13일
플랫폼 제공자 MarkMonitor US(US)
HTTP 상태302 Found (Temporary)
기술 세부 정보Provenance & timestamps
최초 발견2026년 9월 1일
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
142.250.154.132
Network ASN
AS15169
Organization
Google LLC
Observed location
Mountain View, US
Server header
scaffolding on HTTPServer2

네임서버 1

  • ns4.google.com

Location describes the IP network.

TLS 인증서

Issuer
Google Trust Services / WE2
Valid from
2026-08-10 08:38:53
Valid until
2026-11-02 08:38:52
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-13 07:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprinte5d9849ee7b4356add4a6fa767fbe571b3ef8fe1fae66e6b173d889bfe84e27f
Certificate names · 70 SANs
  • blogspot.ae
  • blogspot.al
  • blogspot.am
  • blogspot.ba
  • blogspot.be
  • blogspot.bg
  • blogspot.ca
  • blogspot.ch
  • blogspot.cl
  • blogspot.co.at
  • blogspot.co.id
  • blogspot.co.il
  • blogspot.co.ke
  • blogspot.co.nz
  • blogspot.co.uk
  • blogspot.co.za
  • blogspot.com
  • blogspot.com.ar
  • blogspot.com.au
  • blogspot.com.br
  • blogspot.com.by
  • blogspot.com.co
  • blogspot.com.cy
  • blogspot.com.ee
  • blogspot.com.eg
  • blogspot.com.es
  • blogspot.com.mt
  • blogspot.com.ng
  • blogspot.com.tr
  • blogspot.com.uy
  • blogspot.cz
  • blogspot.de
  • blogspot.dk
  • blogspot.fi
  • blogspot.fr
  • blogspot.gr
  • blogspot.hk
  • blogspot.hr
  • blogspot.hu
  • blogspot.ie
  • blogspot.in
  • blogspot.is
  • blogspot.it
  • blogspot.jp
  • blogspot.kr
  • blogspot.li
  • blogspot.lt
  • blogspot.lu
  • blogspot.md
  • blogspot.mk
  • blogspot.mx
  • blogspot.my
  • blogspot.nl
  • blogspot.no
  • blogspot.pe
  • blogspot.pt
  • blogspot.qa
  • blogspot.ro
  • blogspot.rs
  • blogspot.ru
  • blogspot.se
  • blogspot.sg
  • blogspot.si
  • blogspot.sk
  • blogspot.sn
  • blogspot.tw
  • blogspot.ug
  • blogspot.vn
  • bp.blogspot.com
  • misc-sni.blogspot.com

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 02:16:16 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 02:16:16 UTC
RDAP registration 알 수 없음
Observed timeline last reachable: 2026-10-19 02:16:16 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.
기술 · 5 identified
Detected via Cloudflare Radar · Wappalyzer engine
이 도메인 신고하기 증거를 제출하고 다른 사람들을 보호하는 데 힘을 보태주세요

VirusTotal 분석

10 / 89 보안 공급업체가 이 도메인에 플래그를 지정했습니다.
View on VT
Last analyzed First positive detection Previous stored snapshot: 10 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
ESET
Emsisoft
Lionic
넷크래프트
PhishFort
소포스
Webroot
사이트 성능 분석

Google PageSpeed Insights — mobile performance audit of trezoio-started.blogspot.si · checked Sep 13, 2026

80
Needs Work
Performance
FCP
3.69s
First Contentful Paint
LCP
3.84s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
3.69s
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.

Page titles differ

redirect: raw=redirect_302; http=302; via=https_proxy; location=https://trezoio-started.blogspot.com/; server=GSE

Browser
https://trezoio-started.blogspot.si/
Crawler
Moved Temporarily
trezoio-started.blogspot.si
저장된 결과
Keitaro TDS
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

    이용 불가→접속 가능

Earlier observations 13
  1. Availability monitor · Recorded state

    접속 가능→이용 불가

  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

3 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    10/89 engine detections

    View source
  3. Added to PhishDestroy

    trezoio-started.blogspot.si

    View source

커뮤니티 인텔리전스

커뮤니티 신고 1건

범주IMPERSONATION

Phishing: impersonation, fake affiliation, impersonating Trezor

증거 및 외부 보고서

Community Scam Report — ChainAbuse
1 report filed for trezoio-started.blogspot.si (1 written by a person) · category: Impersonation · source checked
“Phishing: impersonation, fake affiliation, impersonating Trezor”
— reported by Anonymous Trusted reporter on Sep 1, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
심층 분석
Help & reporting

이 사이트로 인해 영향을 받으셨나요?

1 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.

  • 모든 비밀번호 변경 — 이메일, 익스체인지 계정 등, 동일한 비밀번호를 사용하는 모든 것
  • 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 및 도메인 사기꾼이 사용한 (다음과 같은 것들을 포함하여 trezoio-started.blogspot.si)
  • 커뮤니케이션 — 사기꾼이 사용한 이메일, 문자, 전화번호, 사용자 이름

비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.

이 사기 사건을 어디에 신고해야 할까요?

  • 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·왓츠앱·데이트 앱을 통해 몇 주에 걸쳐 신뢰를 쌓은 뒤, 돈을 훔쳐갔다
  • 회복 사기 — 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/ko/embed/domain/trezoio-started.blogspot.si"
  title="PhishDestroy threat report for trezoio-started.blogspot.si"
  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>