HashFast customer e-mail leak

[tacotime]

All HashFast customers appear to have had their email addresses leaked today by the company itself.

Please ensure:
1. Images are turned off in your email client to prevent ip phishing attempts.
2. Reverse email lookups do not reveal your delivery address.
3. You do not open emails that appear to be phishing attempts.

Disclaimer: I am not a paid employee of HashFast but was instead selected to answer questions for them here on bitcointalk -- so please don't emit venom in my direction.

[1715686444]

1715686444

[1715686444]

1715686444

[1715686444]

1715686444

[dhenson]

All HashFast customers appear to have had their email addresses leaked today by the company itself.

Please ensure:
1. Images are turned off in your email client to prevent ip phishing attempts.
2. Reverse email lookups do not reveal your delivery address.
3. You do not open emails that appear to be phishing attempts.

Disclaimer: I am not a paid employee of HashFast but was instead selected to answer questions for them here on bitcointalk -- so please don't emit venom in my direction.

They leaked all of their customer email addresses and are having a non-employee be their communication channel?

[cedivad]

They leaked all of their customer email addresses and are having a non-employee be their communication channel?

Both of them can be seen as good moves... Eg, "i'm not responsible for what he said" and "let's troll them and have them spend the night talking about our stupidity instead of how having them to organise to sue us after this last useless update".

[HarrisonS]

How perfect is it that this email was sent on a Friday, right before they close for 2 days?

[tacotime]

They leaked all of their customer email addresses and are having a non-employee be their communication channel?

Both of them can be seen as good moves... Eg, "i'm not responsible for what he said" and "let's troll them and have them spend the night talking about our stupidity instead of how having them to organise to sue us after this last useless update".

I just don't really want to be affiliated with anything that's going on internally right now with this company.  But everyone needs to know this has happened to protect themselves. HashFast didn't authorize me or tell me to say that this happened, but it is obviously true to anyone who received the latest email newsletter.

[cedivad]

How perfect is it that this email was sent on a Friday, right before they close for 2 days?

Actually i expected you to delay that until Monday night.

Btw, i will quote myself:

We should also ask why their puppet pointed us to that eligius address in the first moment, it's in fact a strange address that is growing a lot - their goal is to have us to lose time, money and strenght over something useless, like the emails or if they are mining with our hardware or not.

What needs to be discussed is:

1) EXWORK vs DELIVERED. I've still to hear back from my lawyer about this, and it is incredibly important. We can't just choose one option in a non rationale way.
2) More proofs of BTC refunds. Is ninjarobot ready to testify pro us in court what they said when he went to visit? Why jjiimm_64 can't share any info about it's mistery email (i asked him if he could share it with a mod).

[cedivad]

@tacotime, can you check the headers of your communication with them? What was their email server?

[dhenson]

I just don't really want to be affiliated with anything that's going on internally right now with this company.  But everyone needs to know this has happened to protect themselves. HashFast didn't authorize me or tell me to say that this happened, but it is obviously true to anyone who received the latest email newsletter.

Ah, thank you for clarifying.  You are in a very un-enviable position.  I suppose you're probably feeling a little bit like theSwede from the Labcoin scam.

However, your phrasing fills me with dread as it appears by your statement that there may be much more going on than we currently know about.

[minternj]

I just don't really want to be affiliated with anything that's going on internally right now with this company.  But everyone needs to know this has happened to protect themselves. HashFast didn't authorize me or tell me to say that this happened, but it is obviously true to anyone who received the latest email newsletter.

Ah, thank you for clarifying.  You are in a very un-enviable position.  I suppose you're probably feeling a little bit like theSwede from the Labcoin scam.

However, your phrasing fills me with dread as it appears by your statement that there may be much more going on than we currently know about.

I doubt taco has much communications with them. Cyberdoc on the other hand disappeared a while back.

[dhenson]

I doubt taco has much communications with them. Cyberdoc on the other hand disappeared a while back.

After being called out as a Hashfast shill/employee, iCeBreaker has been remarkably silent as well.

[minternj]

I doubt taco has much communications with them. Cyberdoc on the other hand disappeared a while back.

After being called out as a Hashfast shill, iCeBreaker has been remarkably silent as well.

Coincidentally the last login of hashfast_cl and icebreaker was on the 25th a couple of hours apart. Fun facts.

[tacotime]

@tacotime, can you check the headers of your communication with them? What was their email server?

Everything by email was from samantha's gmail, and I think she jumped ship a couple of weeks ago.

[thomas_s]

@tacotime, can you check the headers of your communication with them? What was their email server?

Everything by email was from samantha's gmail, and I think she jumped ship a couple of weeks ago.

Still this means that they didn't protect their customers privacy the proper way by allowing one of their employees to have a copy of the emails.

You'd be kind of pissed off if you went to the bank and the teller that helped you copied all of your account information down then used it the next day or after he/she quit wouldn't you.

[HarrisonS]

Sorry! In our rush to update we sent email CC not BCC. We spotted error shortly after, have taken immediate action to prevent future errors!

-Twitter

[thomas_s]

Sorry! In our rush to update we sent email CC not BCC. We spotted error shortly after, have taken immediate action to prevent future errors!

-Twitter

Woot they just admitted to it.

[Xian01]

... was instead selected to answer questions for them here on bitcointalk ...

 Why are you the messenger, and they aren't dealing with this fallout themselves ?

[DyslexicZombei]

What a disaster! Could HF have screwed up this launch any worse?  

I sent trust to dhenson for alerting me to this matter via email with nothing to gain from his action. I suggest that others do the same, if he was the one that also alerted you to this problem.

[dhenson]

What a disaster! Could HF have screwed up this launch any worse?  

I sent trust to dhenson for alerting me to this matter via email with nothing to gain from his action. I suggest that others do the same, if he was the one that also alerted you to this problem.

Thank you for the props, just wish I could have sent the email to everyone effected. (only had access to 2/5 of the list)

[padrino]

Disclaimer: I am not a paid employee of HashFast but was instead selected to answer questions for them here on bitcointalk -- so please don't emit venom in my direction.

I am a little confused on your role here, you are not an employee and was not authorized to say anything yet you state you are "Hashfast Bitcointalk Support" how exactly does that work, especially with matters like this where you and/or Hashfast could get in Legal trouble for speaking out of turn. I am frankly more worried about you since it would be easy to roll you under the bus.

[edgie13]

I  received the update email and my email address was leaked, but funny thing is that I'm not even on batch 1.