Quote from: TwinWinNerD on January 20, 2014, 04:49:39 PM

Quote from: msin on January 20, 2014, 04:48:06 PM

Quote from: TwinWinNerD on January 20, 2014, 04:32:51 PM

Quote from: r3animation on January 20, 2014, 04:23:10 PM

Quote from: msin on January 20, 2014, 04:10:37 PM

Quote from: rickyjames on January 20, 2014, 04:04:27 PM

Quote from: r3animation on January 20, 2014, 03:56:26 PM

Quote from: TwinWinNerD on January 20, 2014, 02:00:36 PM

Quote from: punkrock on January 20, 2014, 01:54:02 PM

Quote from: rickyjames on January 20, 2014, 12:41:22 PM

WE NEED AN ACCOUNT FREEZE CODE CAPABILITY A USER CAN LOAD INTO THE BLOCKCHAIN AS A PAID MESSAGE THAT ALL NODES WILL RECOGNIZE AND REJECT ALL TRANSACTIONS OUT OF THIS ACCOUNT UNTIL A USER REVERSES IT AND TURNS IT OFF WITH A SECOND PASSWORD.

No need to shout, but yes. +1

###

woulda saved me 107000 NXT Sad

Would have saved me 500k NXT. Sad

As a lawyer says to a jury, I rest my case.

Utopianfuture, you could wake up tomorrow to this nightmare. So could I. Dear reader, so could you.

There is a reason for this, both have something in common. I still have some Nxt in an 8 character password (all letters) account and it's still there no problem.

Nope, TwinWinNerD and I discussed it.

Yes.

And the strange thing is, IF they had access to my Keepass database, why did they only target my NXT accounts and not exchange accounts with funds on them? I had a good bunch of money on bitfinex for example. Or use my reputation in various forums to scam people?

I am still not 100% convinced it was a keylogger with access to all my datas. Maybe someone found a way to read the chache of my browser? I never use "Safe mode" for NXT. Maybe i should do that from now on?

I always use the secure 7875 connection, do either of you? Either way, sorry for your loss.

I had problems with early versions, so i always used this bookmark: http://localhost:7874/

Could that be a serious problem?

It could be if a hacker has access to your browser cache, if it's 7875, they wouldn't be able to see anything. It's such an isolated incident, that it may be something you did, but don't remember doing, like accessing your account on a public node address.