Trezor Phishing Website: Difference between revisions
(Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/trezorphishingwebsite.php}} thumb|TrezorA Trezor user reports that they were tricked out of their funds through an attempt to upgrade their wallet software. Instead of visiting the Trezor website, they ended up clicking on Google Ads in the search results, which led them to a scam website. This scam website claimed their wallet was losing connection and they needed to enter the...") |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/trezorphishingwebsite.php}} | {{Imported Case Study 2|source=https://www.quadrigainitiative.com/casestudy/trezorphishingwebsite.php}} | ||
{{Unattributed Sources}} | |||
[[File:Trezor.jpg|thumb|Trezor]]A Trezor user reports that they were tricked out of their funds through an attempt to upgrade their wallet software. Instead of visiting the Trezor website, they ended up clicking on Google Ads in the search results, which led them to a scam website. This scam website claimed their wallet was losing connection and they needed to enter their seed phrase. When they did, it enabled the attacker to steal all of their funds. There is no indication that any funds have been recovered. | [[File:Trezor.jpg|thumb|Trezor]]A Trezor user reports that they were tricked out of their funds through an attempt to upgrade their wallet software. Instead of visiting the Trezor website, they ended up clicking on Google Ads in the search results, which led them to a scam website. This scam website claimed their wallet was losing connection and they needed to enter their seed phrase. When they did, it enabled the attacker to steal all of their funds. There is no indication that any funds have been recovered. | ||
This is a global/international case not involving a specific country. | This is a global/international case not involving a specific country.<ref name="reddit-6786" /><ref name="trezor-6569" /><ref name="trezor-6570" /><ref name="coinmarketcap-623" /><ref name="coinmarketcap-6787" /><ref name="coinmarketcap-4651" /><ref name="blockchaindotcom-6788" /><ref name="blockchair-6789" /><ref name="etherscan-6790" /> | ||
== About Trezor == | == About Trezor == | ||
| Line 31: | Line 32: | ||
Don't Include: | Don't Include: | ||
* Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed. | * Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed. | ||
* Anything that wasn't reasonably knowable at the time of the event. | * Anything that wasn't reasonably knowable at the time of the event. | ||
| Line 52: | Line 52: | ||
!Description | !Description | ||
|- | |- | ||
|November 10th, 2019 1:19:25 AM | |November 10th, 2019 1:19:25 AM MST | ||
| | |Main Event | ||
| | |Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here. | ||
|- | |- | ||
| | | | ||
| Line 64: | Line 60: | ||
| | | | ||
|} | |} | ||
== Technical Details == | |||
This section includes specific detailed technical analysis of any security breaches which happened. What specific software vulnerabilities contributed to the problem and how were they exploited? | |||
== Total Amount Lost == | == Total Amount Lost == | ||
The total amount lost | The total amount lost has been estimated at $9,000 USD. | ||
How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie? | How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie? | ||
| Line 77: | Line 76: | ||
== Total Amount Recovered == | == Total Amount Recovered == | ||
There do not appear to have been any funds recovered in this case. | |||
What funds were recovered? What funds were reimbursed for those affected users? | What funds were recovered? What funds were reimbursed for those affected users? | ||
| Line 83: | Line 82: | ||
== Ongoing Developments == | == Ongoing Developments == | ||
What parts of this case are still remaining to be concluded? | What parts of this case are still remaining to be concluded? | ||
== General Prevention Policies == | |||
== Prevention Policies == | |||
There is no reason to ever enter a seed phrase into an application. All hardware wallets on the market establish that any phrase should be entered into the hardware wallet hardware itself. | There is no reason to ever enter a seed phrase into an application. All hardware wallets on the market establish that any phrase should be entered into the hardware wallet hardware itself. | ||
Always check and visit the official website of a service. The majority of funds should be stored offline and not on a live wallet application. When setting up a new wallet or upgrading wallet software, never enter your pass phrase or send any funds without first transferring a smaller amount. | Always check and visit the official website of a service. The majority of funds should be stored offline and not on a live wallet application. When setting up a new wallet or upgrading wallet software, never enter your pass phrase or send any funds without first transferring a smaller amount. | ||
== Individual Prevention Policies == | |||
{{Prevention:Individuals:Placeholder}} | |||
{{Prevention:Individuals:End}} | |||
== Platform Prevention Policies == | |||
{{Prevention:Platforms:Placeholder}} | |||
{{Prevention:Platforms:End}} | |||
== Regulatory Prevention Policies == | |||
{{Prevention:Regulators:Placeholder}} | |||
{{Prevention:Regulators:End}} | |||
== References == | == References == | ||
[https://www.reddit.com/r/TREZOR/comments/e1a9o1/fake_trezor_website_all_funds_lost/ Reddit - Dive into anything] (Feb 25) | <references><ref name="reddit-6786">[https://www.reddit.com/r/TREZOR/comments/e1a9o1/fake_trezor_website_all_funds_lost/ Reddit - Dive into anything] (Feb 25, 2022)</ref> | ||
[https://trezor.io/ https://trezor.io/] (Feb 20) | <ref name="trezor-6569">[https://trezor.io/ https://trezor.io/] (Feb 20, 2022)</ref> | ||
[https://trezor.io/security/ https://trezor.io/security/] (Feb 20) | <ref name="trezor-6570">[https://trezor.io/security/ https://trezor.io/security/] (Feb 20, 2022)</ref> | ||
[https://coinmarketcap.com/currencies/bitcoin/historical-data/ Bitcoin price today, BTC live marketcap, chart, and info | CoinMarketCap] (May | <ref name="coinmarketcap-623">[https://coinmarketcap.com/currencies/bitcoin/historical-data/ Bitcoin price today, BTC live marketcap, chart, and info | CoinMarketCap] (May 16, 2021)</ref> | ||
[https://coinmarketcap.com/currencies/litecoin/historical-data/ https://coinmarketcap.com/currencies/litecoin/historical-data/] (Mar 1) | <ref name="coinmarketcap-6787">[https://coinmarketcap.com/currencies/litecoin/historical-data/ https://coinmarketcap.com/currencies/litecoin/historical-data/] (Mar 1, 2022)</ref> | ||
[https://coinmarketcap.com/currencies/ethereum/historical-data/ https://coinmarketcap.com/currencies/ethereum/historical-data/] (Dec | <ref name="coinmarketcap-4651">[https://coinmarketcap.com/currencies/ethereum/historical-data/ https://coinmarketcap.com/currencies/ethereum/historical-data/] (Dec 21, 2021)</ref> | ||
[https://www.blockchain.com/btc/tx/f12adec2c682cf56e5d664c6193d349c89e15bb5d1e6fd1adaf959f1d65a73b0 Transaction: f12adec2c682cf56e5d664c6193d349c89e15bb5d1e6fd1adaf959f1d65a73b0 | Blockchain Explorer] (Mar 1) | <ref name="blockchaindotcom-6788">[https://www.blockchain.com/btc/tx/f12adec2c682cf56e5d664c6193d349c89e15bb5d1e6fd1adaf959f1d65a73b0 Transaction: f12adec2c682cf56e5d664c6193d349c89e15bb5d1e6fd1adaf959f1d65a73b0 | Blockchain Explorer] (Mar 1, 2022)</ref> | ||
[https://blockchair.com/litecoin/transaction/aed3444ea7a8869209db734cf94fa54ca80aebc38b1c6d86a3b33e0a4de0b000 Litecoin / Transaction / aed3444ea7a8869209db734cf94fa54ca80aebc38b1c6d86a3b33e0a4de0b000 — Blockchair] (Mar 1) | <ref name="blockchair-6789">[https://blockchair.com/litecoin/transaction/aed3444ea7a8869209db734cf94fa54ca80aebc38b1c6d86a3b33e0a4de0b000 Litecoin / Transaction / aed3444ea7a8869209db734cf94fa54ca80aebc38b1c6d86a3b33e0a4de0b000 — Blockchair] (Mar 1, 2022)</ref> | ||
[https://etherscan.io/tx/0x9d6814af4be3a080552dcc39a85b9f53260a1ba42484a4df160b8c40d529bc21 https://etherscan.io/tx/0x9d6814af4be3a080552dcc39a85b9f53260a1ba42484a4df160b8c40d529bc21] (Mar 1) | <ref name="etherscan-6790">[https://etherscan.io/tx/0x9d6814af4be3a080552dcc39a85b9f53260a1ba42484a4df160b8c40d529bc21 https://etherscan.io/tx/0x9d6814af4be3a080552dcc39a85b9f53260a1ba42484a4df160b8c40d529bc21] (Mar 1, 2022)</ref></references> | ||
Latest revision as of 13:27, 1 May 2023
Notice: This page is a freshly imported case study from the original repository. The original content was in a different format, and may not have relevant information for all sections. Please help restructure the content by moving information from the 'About' and 'General Prevention' sections to other sections, and add any missing information or sources you can find. If you are new here, please read General Tutorial on Wikis or Anatomy of a Case Study for help getting started.
Notice: This page contains sources which are not attributed to any text. The unattributed sources follow the initial description. Please assist by visiting each source, reviewing the content, and placing that reference next to any text it can be used to support. Feel free to add any information that you come across which isn't present already. Sources which don't contain any relevant information can be removed. Broken links can be replaced with versions from the Internet Archive. See General Tutorial on Wikis, Anatomy of a Case Study, and/or Citing Your Sources Guide for additional information. Thanks for your help!
A Trezor user reports that they were tricked out of their funds through an attempt to upgrade their wallet software. Instead of visiting the Trezor website, they ended up clicking on Google Ads in the search results, which led them to a scam website. This scam website claimed their wallet was losing connection and they needed to enter their seed phrase. When they did, it enabled the attacker to steal all of their funds. There is no indication that any funds have been recovered.
This is a global/international case not involving a specific country.[1][2][3][4][5][6][7][8][9]
About Trezor
"The safe place for your coins." "Store your coins with Trezor." "Hardware wallet is the safest way to manage & trade your cryptocurrencies."
"I was trying to move some of my BTC from Trezor to an exchange and there was a notice saying that my Trezor Bridge is out of date."
"So I just googled Trezor bridge to find the latest update, thats when I clicked into the fake Trezor website. Everything looks the same as the legit Trezor.io website, except the popup saying there is a need to recover the wallet due to a bad connection. I did not pay enough attention as I though the poor connection was caused by the outdated Trezor bridge, plus I was trying to upgrade the firmware too as I have not logged into my Trezor for a while. So I was ready to put in the recovery seed anyway and that costs me everything."
"Strongly recommend prohibiting fake web as promoted Ad on google, and a wallet application like ledger live would be great to avoid similar incident on web browser."
"To be more specific, I lost 0.6126 BTC, 44.8362 LTC and 3.4962 ETH."
This is a global/international case not involving a specific country.
The background of the exchange platform, service, or individuals involved, as it would have been seen or understood at the time of the events.
Include:
- Known history of when and how the service was started.
- What problems does the company or service claim to solve?
- What marketing materials were used by the firm or business?
- Audits performed, and excerpts that may have been included.
- Business registration documents shown (fake or legitimate).
- How were people recruited to participate?
- Public warnings and announcements prior to the event.
Don't Include:
- Any wording which directly states or implies that the business is/was illegitimate, or that a vulnerability existed.
- Anything that wasn't reasonably knowable at the time of the event.
There could be more than one section here. If the same platform is involved with multiple incidents, then it can be linked to a main article page.
The Reality
This sections is included if a case involved deception or information that was unknown at the time. Examples include:
- When the service was actually started (if different than the "official story").
- Who actually ran a service and their own personal history.
- How the service was structured behind the scenes. (For example, there was no "trading bot".)
- Details of what audits reported and how vulnerabilities were missed during auditing.
What Happened
The specific events of the loss and how it came about. What actually happened to cause the loss and some of the events leading up to it.
| Date | Event | Description |
|---|---|---|
| November 10th, 2019 1:19:25 AM MST | Main Event | Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here. |
Technical Details
This section includes specific detailed technical analysis of any security breaches which happened. What specific software vulnerabilities contributed to the problem and how were they exploited?
Total Amount Lost
The total amount lost has been estimated at $9,000 USD.
How much was lost and how was it calculated? If there are conflicting reports, which are accurate and where does the discrepancy lie?
Immediate Reactions
How did the various parties involved (firm, platform, management, and/or affected individual(s)) deal with the events? Were services shut down? Were announcements made? Were groups formed?
Ultimate Outcome
What was the end result? Was any investigation done? Were any individuals prosecuted? Was there a lawsuit? Was any tracing done?
Total Amount Recovered
There do not appear to have been any funds recovered in this case.
What funds were recovered? What funds were reimbursed for those affected users?
Ongoing Developments
What parts of this case are still remaining to be concluded?
General Prevention Policies
There is no reason to ever enter a seed phrase into an application. All hardware wallets on the market establish that any phrase should be entered into the hardware wallet hardware itself.
Always check and visit the official website of a service. The majority of funds should be stored offline and not on a live wallet application. When setting up a new wallet or upgrading wallet software, never enter your pass phrase or send any funds without first transferring a smaller amount.
Individual Prevention Policies
No specific policies for individual prevention have yet been identified in this case.
For the full list of how to protect your funds as an individual, check our Prevention Policies for Individuals guide.
Platform Prevention Policies
Policies for platforms to take to prevent this situation have not yet been selected in this case.
For the full list of how to protect your funds as a financial service, check our Prevention Policies for Platforms guide.
Regulatory Prevention Policies
No specific regulatory policies have yet been identified in this case.
For the full list of regulatory policies that can prevent loss, check our Prevention Policies for Regulators guide.
References
- ↑ Reddit - Dive into anything (Feb 25, 2022)
- ↑ https://trezor.io/ (Feb 20, 2022)
- ↑ https://trezor.io/security/ (Feb 20, 2022)
- ↑ Bitcoin price today, BTC live marketcap, chart, and info | CoinMarketCap (May 16, 2021)
- ↑ https://coinmarketcap.com/currencies/litecoin/historical-data/ (Mar 1, 2022)
- ↑ https://coinmarketcap.com/currencies/ethereum/historical-data/ (Dec 21, 2021)
- ↑ Transaction: f12adec2c682cf56e5d664c6193d349c89e15bb5d1e6fd1adaf959f1d65a73b0 | Blockchain Explorer (Mar 1, 2022)
- ↑ Litecoin / Transaction / aed3444ea7a8869209db734cf94fa54ca80aebc38b1c6d86a3b33e0a4de0b000 — Blockchair (Mar 1, 2022)
- ↑ https://etherscan.io/tx/0x9d6814af4be3a080552dcc39a85b9f53260a1ba42484a4df160b8c40d529bc21 (Mar 1, 2022)