VirusTotal
10 / 92 engine detections
Open reporttrezor.wallet.org.ph is a Trezor impersonation page detected by PhishDestroy on 2026-08-25. Risk: critical (88/100). Status: Reachable · access restricted. Hosting: Cloudflare, Inc. VirusTotal: 10/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.
“Attention Required! | Cloudflare”
10 / 92 engine detections
Open reportDBL_PHISH
no community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
trezor.wallet.org.ph is an impersonation phishing site that uses the Trezor brand to target owners of Trezor hardware wallets. It puts the brand name at the front of a Philippine wallet.org.ph address, so a hurried reader sees "trezor" and "wallet" and assumes it is official. PhishDestroy first flagged it on 2026-08-25, and it was still online on 2026-10-19, with its content served behind a protection layer.
Fake Trezor pages usually claim the device needs a firmware update, a security check or a wallet "recovery." They then ask the victim to type the 12- or 24-word recovery seed into a web form. Whoever holds that seed controls the wallet, so the attacker can rebuild it elsewhere and empty it without ever touching the physical device. The page title currently reads "Attention Required! | Cloudflare," which is a Cloudflare challenge screen rather than Trezor branding, while we classify the site as Trezor impersonation.
On 2026-10-07, 10 of 92 VirusTotal engines flagged the domain. Detections came from alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data and PhishFort. PhishFort specializes in crypto-brand protection, so its verdict carries particular weight here. Spamhaus lists the domain in its DBL with the DBL_PHISH tag, which mail filters and DNS resolvers use to block it, and it is on the PhishDestroy blocklist.
The site resolves to 104.26.9.49 on Cloudflare's network, geolocated to Canada. That means the address belongs to Cloudflare's shared front end, not to whoever actually runs the page. Its HTTPS certificate comes from Google Trust Services (WE1), the routine automated certificate for this kind of setup. The padlock in the browser says nothing about whether the site is genuine.
Trezor never asks for your recovery seed on a website, in an app form or by message. If you typed your seed into this site, treat the wallet as compromised. Set up your Trezor again with a freshly generated seed and move all funds to the new addresses immediately. If you downloaded any "Trezor" software from this domain, remove it and scan the machine. Defenders should block the hostname at the DNS, proxy and mail layers, and report it to Cloudflare and Trezor's security team.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a03825-b803-72b8-8f1f-597cb1ccded2 |
|---|---|
| Final url | https://trezor.wallet.org.ph/ |
| Status | 403 |
| Ip | 172.67.74.162 |
| Contacted IP addresses | [
"172.67.74.162"
] |
| Asns | [
"13335"
] |
| Linked domains | [
"www.cloudflare.com"
] |
| Document hash | 1964624430ec55ef357ec38161c46adfd953173e3706214e1c94e193b125c55c |
| Script hashes | [
"4e4a845231637906eae640214acce62f08e845c97b3d0d8823ed7eef5358cb30"
] |
| Globals | [
"_cf_translation"
] |
| Cookies | [
"cf_clearance"
] |
| Tls | {
"san": [
"wallet.org.ph",
"*.wallet.org.ph"
],
"cipher": "AES_128_GCM",
"issuer": "WE1",
"subject": "wallet.org.ph",
"protocol": "TLS 1.3",
"valid_to": "2026-10-01T06:07:54Z",
"valid_from": "2026-07-03T05:07:58Z"
} |
| Domain age days | 53 |
| Apex age days | 74 |
| Tls age days | 53 |
| Tls valid days | 90 |
| Requests | 7 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 64,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "cloudflare",
"content-type": "text/html; charset=UTF-8",
"x-frame-options": "SAMEORIGIN",
"referrer-policy": "same-origin"
} |
Observed: · Retrieved:
| Uuid | f6d7234f-a921-4348-b68d-f5687b8cad9a |
|---|---|
| Final url | https://trezor.wallet.org.ph/ |
| Status | 403 |
| Redirected | https-only |
| History | [
{
"url": "http://trezor.wallet.org.ph/",
"status": 307
},
{
"url": "https://trezor.wallet.org.ph/",
"status": 403
}
] |
| DOM structure hash | e1e0ec04ba2dccd9143717ccf431a0c9d267fac4083951806a2652b5fb5fcf8d |
| Document hash | d7b615dcc6a766eba0064deb5585a1e162def32682f900db43c83f6278f4e12a |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "trezor.wallet.org.ph",
"type": "A",
"value": "104.26.9.49"
},
{
"name": "trezor.wallet.org.ph",
"type": "A",
"value": "104.26.8.49"
},
{
"name": "trezor.wallet.org.ph",
"type": "A",
"value": "172.67.74.162"
},
{
"name": "trezor.wallet.org.ph",
"type": "AAAA",
"value": "2606:4700:20::681a:931"
},
{
"name": "trezor.wallet.org.ph",
"type": "AAAA",
"value": "2606:4700:20::681a:831"
},
{
"name": "trezor.wallet.org.ph",
"type": "AAAA",
"value": "2606:4700:20::ac43:4aa2"
}
] |
| Dnssec valid | false |
| Ip | 104.26.9.49 |
No. PhishDestroy classifies trezor.wallet.org.ph as a Trezor impersonation page (risk: critical, 88/100); it was first detected on 2026-08-25. VirusTotal: 10/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on trezor.wallet.org.ph. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
96b738e341cc9b3b7c7c4797648c09995c9c2c0e78435a43a197a5935575b96ewallet.org.phSaved 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 trezor.wallet.org.ph · checked Aug 25, 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.
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
protected
cloudflare_challenge · Cloudflare · challenge
5→6
4→5
3→4
10/92 engine detections
View sourceNo threat flag
View sourcetrezor.wallet.org.ph
View source74 stored lookalike domains
1 community report
CategoryIMPERSONATION
Phishing: impersonation, impersonating Trezor
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
trezor.wallet.org.ph
“Phishing: impersonation, impersonating Trezor”
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
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 ↗
trezor.wallet.org.ph)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
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
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.