Inputs.io Phishing Attack: Difference between revisions

From Quadriga Initiative Cryptocurrency Hacks, Scams, and Frauds Repository
Jump to navigation Jump to search
No edit summary
(COMPLETE 30 minutes. Updated construction template. Integrated location into description. Spread out information from the about section to other sections. Added information to the timeline about the report from TradeFortress, and corrected the timezone to be the correct UTC time. Updated to remove any template stubs. Filled in the full prevention section for all actors. Cleaned up text and formatting of all sources in the wiki article.)
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/inputsiophishingattack.php}}
{{Case Study Under Construction}}{{Unattributed Sources}}
{{Unattributed Citations}}


[[File:Inputsio.jpg|thumb|Inputs.io]]Inputs.io operated a centralized wallet service. In August 2013, there was a reported phishing attack against users of the platform. Some users of the platform reportedly received an email requesting them to log into a phishing website. It is unclear if private information of platform users was breached and used to target the email. It is also unclear if any funds were lost in the attack.
[[File:Inputsio.jpg|thumb|Inputs.io Logo/Homepage]]Inputs.io operated a centralized wallet service out of Australia. In August 2013, there was a reported phishing attack against users of the platform. Some users of the platform reportedly received an email requesting them to log into a phishing website. It is unclear if private information of platform users was breached and used to target the email. It is also unclear if any funds were lost in the attack.


This exchange or platform is based in Australia, or the incident targeted people primarily in Australia.
<ref name="bitcointalk-7318" /><ref name="bitcointalklegendaryprofiles-6924" /><ref name="inputsarchive-7173" /><ref name="bitcoinwiki-7174" /><ref name="inputsarchive-7175" /><ref name="financearchive-7176" /><ref name="inputsarchive-7177" /><ref name="bitcointalk-7334" />
<ref name="bitcointalk-7318" /><ref name="bitcointalklegendaryprofiles-6924" /><ref name="inputsarchive-7173" /><ref name="bitcoinwiki-7174" /><ref name="inputsarchive-7175" /><ref name="financearchive-7176" /><ref name="inputsarchive-7177" /><ref name="bitcointalk-7334" />


Line 13: Line 11:


"Send bitcoins instantly to an email address - no waiting for confirmations, no fees and no double spending." "Inputs.io Enables Anyone To Send Bitcoin Instantly And Securely" "It's easy and free. We made Bitcoin easy while powerful. Get your secure wallet in 30 seconds. Bitcoin transactions take a hour to confirm. Inputs.io makes it instant with no fees. The most secure wallet ever created. Automatic free mixing for your privacy." "Bitcoin made easy - shave 8 GB of the blockchain off your hard drive, and make a wallet in 30 seconds. Works everywhere - your desktop to mobile." "Off chain transactions are also easier to use. The average user does not want to remember addresses - they want to use Bitcoin like PayPal instead of seeing a "Waiting for 0/6 confirmations"... Zzz."
"Send bitcoins instantly to an email address - no waiting for confirmations, no fees and no double spending." "Inputs.io Enables Anyone To Send Bitcoin Instantly And Securely" "It's easy and free. We made Bitcoin easy while powerful. Get your secure wallet in 30 seconds. Bitcoin transactions take a hour to confirm. Inputs.io makes it instant with no fees. The most secure wallet ever created. Automatic free mixing for your privacy." "Bitcoin made easy - shave 8 GB of the blockchain off your hard drive, and make a wallet in 30 seconds. Works everywhere - your desktop to mobile." "Off chain transactions are also easier to use. The average user does not want to remember addresses - they want to use Bitcoin like PayPal instead of seeing a "Waiting for 0/6 confirmations"... Zzz."
"ALERT: Phishing Site." "Please make sure to check you are on https://inputs.io every time you try to sign in."
"Some people have received [a phishing] email."
"Your account is limited as we suspect that someone has gained unauthorized access to your account. This is a final reminder to activate your account to continue using our services. Else your account will me permanently blocked with all the funds in it. To activate your account please follow the link below and fill in the details."
This exchange or platform is based in Australia, or the incident targeted people primarily in Australia.
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 ==
== The Reality ==
This sections is included if a case involved deception or information that was unknown at the time. Examples include:
Users need to ensure that they are always interacting with the websites which they expect to be interacting.
 
* 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 ==
== 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.
There were reports of phishing attacks on the inputs.io platform.
{| class="wikitable"
{| class="wikitable"
|+Key Event Timeline - Inputs.io Phishing Attack
|+Key Event Timeline - Inputs.io Phishing Attack
Line 55: Line 23:
!Description
!Description
|-
|-
|August 24th, 2013 3:45:15 PM
|August 24th, 2013 9:45:15 AM MDT
|Main Event
|TradeFortress Reports Phishing
|Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here.
|TradeFortress posts a response on the BitcoinTalk thread for inputs.io to announce the phishing attack which has been observed<ref name="bitcointalk-7318" />.
|-
|-
|
|
Line 67: Line 35:
The total amount lost is unknown.
The total amount lost is unknown.


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 ==
"Some people have received [a phishing] email."


== Immediate Reactions ==
"ALERT: Phishing Site." "Please make sure to check you are on https://inputs.io every time you try to sign in."
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 ==
== Ultimate Outcome ==
What was the end result? Was any investigation done? Were any individuals prosecuted? Was there a lawsuit? Was any tracing done?
"Your account is limited as we suspect that someone has gained unauthorized access to your account. This is a final reminder to activate your account to continue using our services. Else your account will me permanently blocked with all the funds in it. To activate your account please follow the link below and fill in the details."


== Total Amount Recovered ==
== Total Amount Recovered ==
There do not appear to have been any funds recovered in this case.
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 ==
== Ongoing Developments ==
What parts of this case are still remaining to be concluded?
The inputs.io platform has been closed down.
== Individual Prevention Policies ==
Individuals always need to be on their guard when any emails are received, and triple check the source. Contact the service via multiple official communication channels if there are any concerns.


== Prevention Policies ==
{{Prevention:Individuals:Protect Personal Information}}
Which policies could have prevented this event from happening?


== References ==
{{Prevention:Individuals:End}}
<references><ref name="bitcointalk-7318">[https://bitcointalk.org/index.php?topic=248803.msg2999245#msg2999245 Inputs.io | Instant Payments, Offchain API, Secure Wallet, 235k+ BTC transferred] (Mar 14, 2022)</ref>


<ref name="bitcointalklegendaryprofiles-6924">[https://bitcointalk.org/index.php?topic=3247239.0 Legendary profiles of bitcointalk.] (Mar 7, 2022)</ref>
== Platform Prevention Policies ==
{{Prevention:Platforms:Cryptocurrency Safety Quiz}}


<ref name="inputsarchive-7173">[https://web.archive.org/web/20131103180145/https://inputs.io/ Inputs.io - Free and Secure Bitcoin Wallet for Everyone] (Mar 14, 2022)</ref>
{{Prevention:Platforms:Establish Industry Insurance Fund}}


<ref name="bitcoinwiki-7174">[https://en.bitcoin.it/wiki/Inputs.io Inputs.io - Bitcoin Wiki] (Mar 14, 2022)</ref>
{{Prevention:Platforms:End}}


<ref name="inputsarchive-7175">[https://web.archive.org/web/20131023051930/https://inputs.io/faq Inputs.io - Free and Secure Bitcoin Wallet for Everyone] (Mar 14, 2022)</ref>
== Regulatory Prevention Policies ==
{{Prevention:Regulators:Cryptocurrency Education Mandate}}


<ref name="financearchive-7176">[https://web.archive.org/web/20130904060353/http://finance.boston.com/boston/news/read/24741186/online_bitcoin_wallet_service_inputs.io_enables_anyone_to_send_bitcoin_instantly_and_securely Online Bitcoin Wallet Service Inputs.io Enables Anyone To Send Bitcoin Instantly And Securely | Stock Market Summary (NSDQ, NYSE, AMEX and more) on Boston.com] (Mar 14, 2022)</ref>
{{Prevention:Regulators:Establish Industry Insurance Fund}}


<ref name="inputsarchive-7177">[https://web.archive.org/web/20131028143853/https://inputs.io/ Inputs.io - Free and Secure Bitcoin Wallet for Everyone] (Mar 14, 2022)</ref>
{{Prevention:Regulators:End}}


<ref name="bitcointalk-7334">[https://bitcointalk.org/index.php?topic=283756.220 CoinLenders Script :: Bitcoin Bank (Borrow+Deposit) Software :: Demo Available] (Mar 20, 2022)</ref></references>
== References ==
<references>
<ref name="bitcointalk-7318">[https://bitcointalk.org/index.php?topic=248803.msg2999245#msg2999245 TradeFortress - "ALERT: Phishing Site Please make sure to check you are on http'''s'''://inputs'''.io''' every time you try to sign in." - BitcoinTalk] (Accessed Mar 14, 2022)</ref>
<ref name="bitcointalklegendaryprofiles-6924">[https://bitcointalk.org/index.php?topic=3247239.0 Legendary profiles of bitcointalk. - BitcoinTalk] (Mar 7, 2022)</ref>
<ref name="inputsarchive-7173">[https://web.archive.org/web/20131103180145/https://inputs.io/ Inputs.io - Free and Secure Bitcoin Wallet for Everyone - Homepage Archive November 3rd, 2013 11:01:45 AM MST] (Accessed Mar 14, 2022)</ref>
<ref name="bitcoinwiki-7174">[https://en.bitcoin.it/wiki/Inputs.io Inputs.io - Bitcoin Wiki] (Accessed Mar 14, 2022)</ref>
<ref name="inputsarchive-7175">[https://web.archive.org/web/20131023051930/https://inputs.io/faq Inputs.io - Free and Secure Bitcoin Wallet for Everyone Archive October 22nd, 2013 11:19:30 PM MDT] (Accessed Mar 14, 2022)</ref>
<ref name="financearchive-7176">[https://web.archive.org/web/20130904060353/http://finance.boston.com/boston/news/read/24741186/online_bitcoin_wallet_service_inputs.io_enables_anyone_to_send_bitcoin_instantly_and_securely Online Bitcoin Wallet Service Inputs.io Enables Anyone To Send Bitcoin Instantly And Securely - Boston.com] (Accessed Mar 14, 2022)</ref>
<ref name="inputsarchive-7177">[https://web.archive.org/web/20131028143853/https://inputs.io/ Inputs.io - Free and Secure Bitcoin Wallet for Everyone Archive October 28th, 2013 8:38:53 AM MDT] (Accessed Mar 14, 2022)</ref>
<ref name="bitcointalk-7334">[https://bitcointalk.org/index.php?topic=283756.220 CoinLenders Script :: Bitcoin Bank (Borrow+Deposit) Software :: Demo Available - BitcoinTalk] (Accessed Mar 20, 2022)</ref>
</references>

Latest revision as of 16:58, 18 October 2024

Notice: This page is a new case study and some aspects have not been fully researched. Some sections may be incomplete or reflect inaccuracies present in initial sources. Please check the References at the bottom for further information and perform your own additional assessment. Please feel free to contribute by adding any missing information or sources you come across. 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!

Inputs.io Logo/Homepage

Inputs.io operated a centralized wallet service out of Australia. In August 2013, there was a reported phishing attack against users of the platform. Some users of the platform reportedly received an email requesting them to log into a phishing website. It is unclear if private information of platform users was breached and used to target the email. It is also unclear if any funds were lost in the attack.

[1][2][3][4][5][6][7][8]

About Inputs.io

"In Early 2013 Inputs.io was launched; a free online Bitcoin wallet and anonymous Bitcoin transfer network: featuring instant off chain Bitcoin transfers and embedded automatic untraceable 'mixing' of all Bitcoin transactions. Featuring truly instant, anonymous and highly secure Bitcoin transactions, the inputs.io platform brings a plethora of key innovations to the table, setting a new benchmark for online Bitcoin wallet services. Anyone worldwide can open an inputs.io online wallet in 30 seconds or less."

"TradeFortress created a free online bitcoin wallet (Inputs.io)." "Inputs.io was a free Bitcoin web wallet that leveraged its own off chain payment network. Inputs implemented numerous security measures, and featured instant, fee-less offchain confirmations with an easy to implement developer API." "Inputs.io is a new bitcoin payment processor leveraging an offchain payment network."

"Send bitcoins instantly to an email address - no waiting for confirmations, no fees and no double spending." "Inputs.io Enables Anyone To Send Bitcoin Instantly And Securely" "It's easy and free. We made Bitcoin easy while powerful. Get your secure wallet in 30 seconds. Bitcoin transactions take a hour to confirm. Inputs.io makes it instant with no fees. The most secure wallet ever created. Automatic free mixing for your privacy." "Bitcoin made easy - shave 8 GB of the blockchain off your hard drive, and make a wallet in 30 seconds. Works everywhere - your desktop to mobile." "Off chain transactions are also easier to use. The average user does not want to remember addresses - they want to use Bitcoin like PayPal instead of seeing a "Waiting for 0/6 confirmations"... Zzz."

The Reality

Users need to ensure that they are always interacting with the websites which they expect to be interacting.

What Happened

There were reports of phishing attacks on the inputs.io platform.

Key Event Timeline - Inputs.io Phishing Attack
Date Event Description
August 24th, 2013 9:45:15 AM MDT TradeFortress Reports Phishing TradeFortress posts a response on the BitcoinTalk thread for inputs.io to announce the phishing attack which has been observed[1].

Total Amount Lost

The total amount lost is unknown.

Immediate Reactions

"Some people have received [a phishing] email."

"ALERT: Phishing Site." "Please make sure to check you are on https://inputs.io every time you try to sign in."

Ultimate Outcome

"Your account is limited as we suspect that someone has gained unauthorized access to your account. This is a final reminder to activate your account to continue using our services. Else your account will me permanently blocked with all the funds in it. To activate your account please follow the link below and fill in the details."

Total Amount Recovered

There do not appear to have been any funds recovered in this case.

Ongoing Developments

The inputs.io platform has been closed down.

Individual Prevention Policies

Individuals always need to be on their guard when any emails are received, and triple check the source. Contact the service via multiple official communication channels if there are any concerns.

Set up separate email addresses for each service, and avoid providing your phone number whenever possible. Any received emails or phone calls must be viewed with scrutiny, especially if unsolicited. Interact with companies only through their official websites and confirm anything with the company directly via multiple official sources, especially if it promises a significant incentive to take an action or threatens access to your funds if an action is not taken. It would be recommended to also establish a network of multiple trusted individuals who use the same services and have a strong level of security knowledge.

For the full list of how to protect your funds as an individual, check our Prevention Policies for Individuals guide.

Platform Prevention Policies

Never take for granted the limited knowledge of users of your service and their tendency to skip past provided information. It is recommended to design a simple tutorial and quiz for new users which explains the basics of seed phrases, strong password generation, secure two-factor authentication, common fraud schemes, how ponzi schemes work, as well as other risks which are unique to the cryptocurrency space. This tutorial and quiz should ensure their understanding and be a standard part of the sign-up or download process which is difficult or impossible to skip.

Work with other industry platforms to set up a multi-signature wallet with private keys held separately by delegate signatories from seven prominent platforms and services within the industry. Establish requirements for contributions by all platforms and services, designed to be affordable for small platforms yet large enough to cover anticipated breach events. Any breach event can be brought forth by a member platform or a petition of 100 signatures for consideration by the delegate signatories. A vote of 4 or more delegate signatures is required to release any funds, which could partially or fully restore lost funds based on their assessment.

For the full list of how to protect your funds as a financial service, check our Prevention Policies for Platforms guide.

Regulatory Prevention Policies

Create a standard tutorial and quiz for all new cryptocurrency participants, which is required to be completed once per participant. This tutorial and quiz should cover the basics of proper seed phrase protection, strong password generation, secure two-factor authentication, common fraud schemes, how to detect and guard against phishing attacks, how ponzi schemes work, as well as other risks which are unique to the cryptocurrency space.

Set up a multi-signature wallet with private keys held separately by delegate signatories from seven prominent platforms and services within the industry. Establish requirements for contributions by all platforms and services within the country, designed to be affordable for small platforms yet large enough to cover anticipated breach events. Any breach event can be brought forth by a member platform or a petition of 100 signatures for consideration by the delegate signatories. A vote of 4 or more delegate signatures is required to release any funds, which could partially or fully restore lost funds based on their assessment.

For the full list of regulatory policies that can prevent loss, check our Prevention Policies for Regulators guide.

References