Topic: CoinLenders, Inputs.io, Tradefortress (HACK) - page 12. (Read 39725 times)
just lol
Well, after some haggling I was able to settle with TradeFortress for 199.383xbt. While it's a pretty terrible outcome, at least I can put this mess behind me, and hopefully preserve my purchasing power in the face of the volatile bitcoin market.
I'll continue to update this thread, but any legal action will have to come from another party, as I no longer have any stake in the matter.
These were the transactions;
e1ec1cb240ba9eac5e845fb8cd342372cb00b307d1b845307b2666d1e8a9d010
c2da4a08c7f01f4ca599ab75594d3510abffa0db0f52a1c4f0349eded37cc772
Perhaps as a result of this deal TradeFortress can offer a better proportion of your deposits back.
I'll continue to update this thread, but any legal action will have to come from another party, as I no longer have any stake in the matter.
These were the transactions;
e1ec1cb240ba9eac5e845fb8cd342372cb00b307d1b845307b2666d1e8a9d010
c2da4a08c7f01f4ca599ab75594d3510abffa0db0f52a1c4f0349eded37cc772
Perhaps as a result of this deal TradeFortress can offer a better proportion of your deposits back.
I'm another one to be added to the Coinlenders owed list: 86.93779676 BTC
I was in email contact with TF last week but he's not replied for quite a number of days now.
Are there any/many CL users in the UK that are looking in to any possible legal remedy?
I was in email contact with TF last week but he's not replied for quite a number of days now.
Are there any/many CL users in the UK that are looking in to any possible legal remedy?
Is anyone else thinking that TF may be hoping to sell remaining coins and buy back after crash to reimburse his creditors?
I mean I wanted to do that with my Coin this time round and not wait for the next bubble.
I mean I wanted to do that with my Coin this time round and not wait for the next bubble.
I was actually thinking exactly the same earlier today.
Not that I personally would dare to do it, but hey, he's got the track reckord of gambling with high stakes...
I hope he didn't sell already.
It's kind of a no-lose bet. If there is a downturn, pay off, keep the profits, and live to scam again. If no downturn, keep the profits and vanish.
There is a possibility that Paymium/Bitcoin-Central did exactly this with the Instawallet funding. Of course we'll likely never know.
Is anyone else thinking that TF may be hoping to sell remaining coins and buy back after crash to reimburse his creditors?
I mean I wanted to do that with my Coin this time round and not wait for the next bubble.
I mean I wanted to do that with my Coin this time round and not wait for the next bubble.
I was actually thinking exactly the same earlier today.
Not that I personally would dare to do it, but hey, he's got the track reckord of gambling with high stakes...
I hope he didn't sell already.
Is anyone else thinking that TF may be hoping to sell remaining coins and buy back after crash to reimburse his creditors?
I mean I wanted to do that with my Coin this time round and not wait for the next bubble.
I mean I wanted to do that with my Coin this time round and not wait for the next bubble.
Are you guys serious or sarcastic? (serious question, i don't want to sound rude)
[/quote]
Dead serious. If you notice, most of the people posting useless smug blather either aren't on the list at the beginning of this thread or have very little at stake. Many of us who do realize that our best chance of getting it back is trying to make sure CL doesn't go under. Of course we don't *know* that TF isn't a scammer, but neither do others *know* that he is. Honest people can disagree, but calling someone a sockpuppet just because he disagrees with you is just being an asshole. The way I figure it, if we can get anywhere near 4000 coins committed to staying in CL -in exchange for veriable assurances that we're likely to be paid back in full later on- and TF still doesn't respond, then we can be pretty confident he's scamming us or fucked up so badly that it doesn't matter. And then we can go after him for whatever we can get.
Are you guys serious or sarcastic? (serious question, i don't want to sound rude)
I am serious.
I want as many of my coins back as possible, and I see no other alternative to achieve this goal.
TradeFortress: I'm with the rest of your creditors. Better for you and us if we work out an arrangement. Try reaching out.
But be certain that I will join other actions against you if you outright stiff us.
Then again the law might get to you first.
But be certain that I will join other actions against you if you outright stiff us.
Then again the law might get to you first.
Same here, I'm willing to leave my btc's with TF for quite some time, and also help out with anything I can.
TradeFortress: I'm with the rest of your creditors. Better for you and us if we work out an arrangement. Try reaching out.
But be certain that I will join other actions against you if you outright stiff us.
Then again the law might get to you first.
But be certain that I will join other actions against you if you outright stiff us.
Then again the law might get to you first.
Same here, I'm willing to leave my btc's with TF for quite some time, and also help out with anything I can.
Ya, I'm sure TF will be happy to pay the losers off if Bitcoin keeps climbing and each BTC becomes worth $5000 :^) Good luck with that.
The victims (probably not the sock puppets who post these things) best hope is that we have another price collapse and TF takes a few bucks he made from the stolen coins to buy back in and clear his name.
TradeFortress: I'm with the rest of your creditors. Better for you and us if we work out an arrangement. Try reaching out.
But be certain that I will join other actions against you if you outright stiff us.
Then again the law might get to you first.
But be certain that I will join other actions against you if you outright stiff us.
Then again the law might get to you first.
Same here, I'm willing to leave my btc's with TF for quite some time, and also help out with anything I can.
You're doing a great job, Dumbfruit. I'm a dual US/NZ citizen, and I'll certainly join you in a class-action if it comes to that. But I don't think the time is now. Frankly, at this point I think the money would be better spent on a good private investigator in Sydney. I'd' still like to know if anyone on this forum knows TF's name.
TF: It should be pretty clear to you that time is running out. I still stand by what I told you in an email: I'm willing to leave my coins in longer-term with some verifiable assurances that I'm likely to be paid back in full later on. By my count, there are some 1500 coins potentially available to you (from JohnHarmer, TomJeff and other relative minnows like me) should you reach out directly to your investors. We're by far the best friends you have here
TradeFortress: I'm with the rest of your creditors. Better for you and us if we work out an arrangement. Try reaching out.
But be certain that I will join other actions against you if you outright stiff us.
Then again the law might get to you first.
TF: It should be pretty clear to you that time is running out. I still stand by what I told you in an email: I'm willing to leave my coins in longer-term with some verifiable assurances that I'm likely to be paid back in full later on.
+1
~'lets give FT time'
+1
...
Finally, @ all the annoying dickheads who think that anyone who disagrees with a tar-and-feather approach to this whole fiasco is a shill for Tradefortress....
STFU!!
Ya OK sure. Whatever you say Socrates.
Thanks plugging away, Dumbfruit. I am happy to hear that TF got back to you with some specifics. Hopefully that means he is meaning to make good to the best of his abilities. I do wish that he would give that as a specific reassurance.
+1
You're doing a great job, Dumbfruit. I'm a dual US/NZ citizen, and I'll certainly join you in a class-action if it comes to that. But I don't think the time is now. Frankly, at this point I think the money would be better spent on a good private investigator in Sydney. I'd' still like to know if anyone on this forum knows TF's name.
TF: It should be pretty clear to you that time is running out. I still stand by what I told you in an email: I'm willing to leave my coins in longer-term with some verifiable assurances that I'm likely to be paid back in full later on. By my count, there are some 1500 coins potentially available to you (from JohnHarmer, TomJeff and other relative minnows like me) should you reach out directly to your investors. We're by far the best friends you have here
Finally, @ all the annoying dickheads who think that anyone who disagrees with a tar-and-feather approach to this whole fiasco is a shill for Tradefortress....
STFU!!
Woe he just answered all my questions fairly quickly and thoroughly in an email! This is exciting!
Will update shortly.
Maybe he just responds better to direct and specific questions...
Will update shortly.
Maybe he just responds better to direct and specific questions...
Stockholm Syndrome?
He responds because the hack was executed "perfectly" and there is nothing to hide.
Ask him about the specific financials and see how quiet he is.
Quote from: TradeFortress
Oct 23th PST time (24th Aus time). A second hack occurred on the Oct 26th (the other 160 BTC).
The compromise was done through compromising multiple of my old email addresses in a chain (compromise one which was the recovery email for another), which led them to [email protected] which received emails forwarded from [email protected]. The attacker was able to reset Linode and Apis networks passwords. Email forwarding was disabled on the 26th (PST, 27th Aus).
I've already posted login logs for Linode on bitcointalk, I've attached logins for apisnetworks which were also reset.
5: Yes, to linode manager. The attacker on the Oct 26th used Lish to skip linode manager and directly shell into the Linode, bypassing 2FA on the manager.
4: The incomplete logs were obtained through lish logview's buffer. The attacker installed mc (midnight commander) and used it to transfer files containing credentials via FTP to 0;[email protected]:[email protected]. From the midnight commander view, the remote server also has another bit.php file not from Inputs. I speculate that this is taken from another service.
3: I do not see where I have access linode password reset logs. I've sent a support ticket to linode requesting such, and authorizing them to provide it to anyone who asks. Ticket ID 2560514
The compromise was done through compromising multiple of my old email addresses in a chain (compromise one which was the recovery email for another), which led them to [email protected] which received emails forwarded from [email protected]. The attacker was able to reset Linode and Apis networks passwords. Email forwarding was disabled on the 26th (PST, 27th Aus).
I've already posted login logs for Linode on bitcointalk, I've attached logins for apisnetworks which were also reset.
5: Yes, to linode manager. The attacker on the Oct 26th used Lish to skip linode manager and directly shell into the Linode, bypassing 2FA on the manager.
4: The incomplete logs were obtained through lish logview's buffer. The attacker installed mc (midnight commander) and used it to transfer files containing credentials via FTP to 0;[email protected]:[email protected]. From the midnight commander view, the remote server also has another bit.php file not from Inputs. I speculate that this is taken from another service.
3: I do not see where I have access linode password reset logs. I've sent a support ticket to linode requesting such, and authorizing them to provide it to anyone who asks. Ticket ID 2560514
It's a lot to digest... I'll update my opening post tomorrow.
Its still missing all the relevant information and that it took him 1 month to just give these informations is more then disappointing. To be honest if i had 200k+ invested into this at the moment i would demand to have his real-id just so i could get a hold of him.
Another thing is that you really wanna stop the class-action lawsuit in light of these response? What after all beside that the hacker installed mc wasnt known before? I seriously start believing you are just another sockpuppet if that happens.
The situation is, even a victim believes TF is a scammer, still the victim is not willing to take any legal action since the loss would be bigger.
Quote from: TradeFortress
Oct 23th PST time (24th Aus time). A second hack occurred on the Oct 26th (the other 160 BTC).
The compromise was done through compromising multiple of my old email addresses in a chain (compromise one which was the recovery email for another), which led them to [email protected] which received emails forwarded from [email protected]. The attacker was able to reset Linode and Apis networks passwords. Email forwarding was disabled on the 26th (PST, 27th Aus).
I've already posted login logs for Linode on bitcointalk, I've attached logins for apisnetworks which were also reset.
5: Yes, to linode manager. The attacker on the Oct 26th used Lish to skip linode manager and directly shell into the Linode, bypassing 2FA on the manager.
4: The incomplete logs were obtained through lish logview's buffer. The attacker installed mc (midnight commander) and used it to transfer files containing credentials via FTP to 0;[email protected]:[email protected]. From the midnight commander view, the remote server also has another bit.php file not from Inputs. I speculate that this is taken from another service.
3: I do not see where I have access linode password reset logs. I've sent a support ticket to linode requesting such, and authorizing them to provide it to anyone who asks. Ticket ID 2560514
The compromise was done through compromising multiple of my old email addresses in a chain (compromise one which was the recovery email for another), which led them to [email protected] which received emails forwarded from [email protected]. The attacker was able to reset Linode and Apis networks passwords. Email forwarding was disabled on the 26th (PST, 27th Aus).
I've already posted login logs for Linode on bitcointalk, I've attached logins for apisnetworks which were also reset.
5: Yes, to linode manager. The attacker on the Oct 26th used Lish to skip linode manager and directly shell into the Linode, bypassing 2FA on the manager.
4: The incomplete logs were obtained through lish logview's buffer. The attacker installed mc (midnight commander) and used it to transfer files containing credentials via FTP to 0;[email protected]:[email protected]. From the midnight commander view, the remote server also has another bit.php file not from Inputs. I speculate that this is taken from another service.
3: I do not see where I have access linode password reset logs. I've sent a support ticket to linode requesting such, and authorizing them to provide it to anyone who asks. Ticket ID 2560514
It's a lot to digest... I'll update my opening post tomorrow.
Its still missing all the relevant information and that it took him 1 month to just give these informations is more then disappointing. To be honest if i had 200k+ invested into this at the moment i would demand to have his real-id just so i could get a hold of him.
Another thing is that you really wanna stop the class-action lawsuit in light of these response? What after all beside that the hacker installed mc wasnt known before? I seriously start believing you are just another sockpuppet if that happens.
Thanks plugging away, Dumbfruit. I am happy to hear that TF got back to you with some specifics. Hopefully that means he is meaning to make good to the best of his abilities. I do wish that he would give that as a specific reassurance.
Thanks Dumbfruit!
Now is time for TF to verify the amounts owed to everybody involved and start allowing some withdrawals. For me even a 1% withdrawal (2.26 BTC) will mean the difference between having a really hard time from now on or having 1 more month to manage how to pay my bills.
Now is time for TF to verify the amounts owed to everybody involved and start allowing some withdrawals. For me even a 1% withdrawal (2.26 BTC) will mean the difference between having a really hard time from now on or having 1 more month to manage how to pay my bills.
Jump to: