Inputs.io Phishing Attack - Revision history

Azoundria: 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.

2024-10-18T22:58:35Z

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.

Show changes

Azoundria at 23:53, 12 April 2023

2023-04-12T23:53:54Z

← Older revision		Revision as of 17:53, 12 April 2023
Line 1:		Line 1:
	{{Imported Case Study\|source=https://www.quadrigainitiative.com/casestudy/inputsiophishingattack.php}}		{{Imported Case Study\|source=https://www.quadrigainitiative.com/casestudy/inputsiophishingattack.php}}
	{{Unattributed ~~Citations~~}}		{{Unattributed Sources}}

	[[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]]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.

	This exchange or platform is based in Australia, or the incident targeted people primarily in Australia.		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" />

	== About Inputs.io ==		== About Inputs.io ==
Line 55:		Line 54:
	!Description		!Description
	\|-		\|-
	\|August 24th, 2013 3:45:15 PM		\|August 24th, 2013 3:45:15 PM MDT
	\|Main Event		\|Main Event
	\|Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here.		\|Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here.
Line 82:		Line 81:
	== 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?
			== 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 ~~Policies ==~~		{{Prevention:Regulators:End}}
	~~Which policies could have prevented this event from happening?~~

	== References ==		== References ==

Azoundria at 23:57, 18 February 2023

2023-02-18T23:57:56Z

← Older revision		Revision as of 17:57, 18 February 2023
Line 1:		Line 1:
	{{Imported Case Study\|source=https://www.quadrigainitiative.com/casestudy/inputsiophishingattack.php}}		{{Imported Case Study\|source=https://www.quadrigainitiative.com/casestudy/inputsiophishingattack.php}}
			{{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]]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.

	This exchange or platform is based in Australia, or the incident targeted people primarily in Australia.		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" />

	== About Inputs.io ==		== About Inputs.io ==
Line 33:		Line 35:

	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 55:		Line 56:
	\|-		\|-
	\|August 24th, 2013 3:45:15 PM		\|August 24th, 2013 3:45:15 PM
	\|~~First~~ Event		\|Main Event
	\|~~This is an expanded~~ description of what happened and the impact. If multiple lines are necessary, add them here.		\|Expand this into a brief description of what happened and the impact. If multiple lines are necessary, add them here.
	\|-
	\|
	\|
	\|
	\|-		\|-
	\|		\|
Line 79:		Line 76:

	== Total Amount Recovered ==		== Total Amount Recovered ==
	~~It is unknown how much was~~ 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 87:		Line 84:

	== Prevention Policies ==		== Prevention Policies ==
			Which policies could have prevented this event from happening?

	== References ==		== References ==
	[https://bitcointalk.org/index.php?topic=248803.msg2999245#msg2999245 Inputs.io \| Instant Payments, Offchain API, Secure Wallet, 235k+ BTC transferred] (Mar 14)		<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>

	[https://bitcointalk.org/index.php?topic=3247239.0 Legendary profiles of bitcointalk.] (Mar 7)		<ref name="bitcointalklegendaryprofiles-6924">[https://bitcointalk.org/index.php?topic=3247239.0 Legendary profiles of bitcointalk.] (Mar 7, 2022)</ref>

	[https://web.archive.org/web/20131103180145/https://inputs.io/ Inputs.io - Free and Secure Bitcoin Wallet for Everyone] (Mar 14)		<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>

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

	[https://web.archive.org/web/20131023051930/https://inputs.io/faq Inputs.io - Free and Secure Bitcoin Wallet for Everyone] (Mar 14)		<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>

	[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)		<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>

	[https://web.archive.org/web/20131028143853/https://inputs.io/ Inputs.io - Free and Secure Bitcoin Wallet for Everyone] (Mar 14)		<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>

	[https://bitcointalk.org/index.php?topic=283756.220 CoinLenders Script :: Bitcoin Bank (Borrow+Deposit) Software :: Demo Available] (Mar 20)		<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>

Azoundria: Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/inputsiophishingattack.php}} Inputs.ioInputs.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...."

2023-01-21T20:00:01Z

Created page with "{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/inputsiophishingattack.php}} thumb|Inputs.ioInputs.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...."

New page

{{Imported Case Study|source=https://www.quadrigainitiative.com/casestudy/inputsiophishingattack.php}}

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

This exchange or platform is based in Australia, or the incident targeted people primarily in Australia.

== 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."

"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 ==
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.
{| class="wikitable"
|+Key Event Timeline - Inputs.io Phishing Attack
!Date
!Event
!Description
|-
|August 24th, 2013 3:45:15 PM
|First Event
|This is an expanded description of what happened and the impact. If multiple lines are necessary, add them here.
|-
|
|
|
|-
|
|
|
|}

== Total Amount Lost ==
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 ==
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 ==
It is unknown how much was recovered.

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?

== Prevention Policies ==

== References ==
[https://bitcointalk.org/index.php?topic=248803.msg2999245#msg2999245 Inputs.io | Instant Payments, Offchain API, Secure Wallet, 235k+ BTC transferred] (Mar 14)

[https://bitcointalk.org/index.php?topic=3247239.0 Legendary profiles of bitcointalk.] (Mar 7)

[https://web.archive.org/web/20131103180145/https://inputs.io/ Inputs.io - Free and Secure Bitcoin Wallet for Everyone] (Mar 14)

[https://en.bitcoin.it/wiki/Inputs.io Inputs.io - Bitcoin Wiki] (Mar 14)

[https://web.archive.org/web/20131023051930/https://inputs.io/faq Inputs.io - Free and Secure Bitcoin Wallet for Everyone] (Mar 14)

[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)

[https://web.archive.org/web/20131028143853/https://inputs.io/ Inputs.io - Free and Secure Bitcoin Wallet for Everyone] (Mar 14)

[https://bitcointalk.org/index.php?topic=283756.220 CoinLenders Script :: Bitcoin Bank (Borrow+Deposit) Software :: Demo Available] (Mar 20)