Comment by exikyut | Hacker News Reader

Comment by exikyut | Hacker News Reader

Parent Full thread

This is being downvoted, but in the process of trying to disprove this I actually discovered it could be true.

Two recent stargazers are http://archive.is/cbPm1 and http://archive.is/o0uzH; both accounts are in "cn" and use an email address with an invalid TLD.

Another two, http://archive.is/x5IBA and http://archive.is/KUnOg, have less "definitely spam" indicators; the only thing they have in common is that x64dbg is the only repo they've starred, that they have no other activity, and that they were created ~two days ago.

Have fun poking through the stargazer list.

I'm very curious as to explanations. Right now I'm not sure whether to wonder if this HN submission is a stargazer-generating demonstration or if I'm just seeing normal github activity (where "normal" means "spammers doing their weird thing").

I think there might actually be something going on weird with this project on Github's end. I've never heard of this project but started getting alerts in my email for it this morning. My account has apparently stared and watched this project. I hadn't used that account for awhile and the security page for my account doesn't show any logins for my account except from this morning, which leads me to believe that it probably wasn't compromised.

The same happened with my Github account.

Same here, been getting lots of emails regarding issues I've supposedly followed for the past few hours. It's got me worried a bit as security audit log shows nothing. Something stinks so think I'll change my password to be safe.

Same with me as well, nothing in the security log. Something is definitely wrong here, how could I get subscribed to issues on a project I've never heard of. Was my account compromised? I've even had 2 Factor Authentication enabled since July 2017.

I received a notification today from Github indicating my account was compromised and reached out on why it did not display in my security status. They indicated that the account was accessed via API and that I should enable two factor.

Why raises the question -- how were YOU compromised with 2 factor on?

i don't know, i like this debugger

Note that I have no issue with x64dbg and don't suspect the project. See the other very strange comments elsewhere in this subthread

Reply on news.ycombinator.com