What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Attention to all users that have no AV installed and downloaded HB/DB past 24 hours

What's even awesomer right now is that battle.net is down and you can't change your passwords right now just in case.... Ugh.
 
they cleaned out the build 557 and its safe to use and stable now. dont get hung up on build 560. if your having issues downloading the latest (557) is perfectly ok.
 
I decided to go back to an earlier and safe version of HB and leave things to settle for 24 hours before downloading the lates (safe and clean) version. Here's the result. I really don't enjoy making negative comments but this just isn't acceptable. Not impressed at all.

View attachment 90642
 
I decided to go back to an earlier and safe version of HB and leave things to settle for 24 hours before downloading the lates (safe and clean) version. Here's the result. I really don't enjoy making negative comments but this just isn't acceptable. Not impressed at all.

View attachment 90642
we are investigating the issue right now, please be patient, but feel free to delete the infected file.
 
Thanks. Could you make a Notice / Sticky somewhere on the main forum when things are back to normal. With so many "FAIL" threads floating around it gets confusing for an old bugger like me to figure out what's happening. Cheers.
 
Thanks. Could you make a Notice / Sticky somewhere on the main forum when things are back to normal. With so many "FAIL" threads floating around it gets confusing for an old bugger like me to figure out what's happening. Cheers.
this is the main notice, since its only effecting our honorbuddy product theres no need to make more threads dedicated to the issue.
 
did hb just get infected again? I noticed it made an update about 15 minutes ago, whats going on?
 
did hb just get infected again? I noticed it made an update about 15 minutes ago, whats going on?
if you have build 558 delete it immediately. we have taken the new update server down for the time being. please be patient.
 
I don't remember seeing my bot update at all, does that mean I should be ok?
 
I don't remember seeing my bot update at all, does that mean I should be ok?
the update wasnt pushed out. so if anyone was effected it would only be someone who downloaded directly, in the last hour or so.
 
No it was .557 which was modified yesterday, the actual release build.

As soon as i saw that, i removed the modified .557, which caused the Server to pull back to .555

After that we made a new build, .560, scanned it and released it. Also scanned all our servers and found the intruder and eliminated it.

How the hell can you say that you have removed v. .557 before 10:01 when I download .557 from the frontpage after a talk with Tony at around 15:40, where he wanted me to donwnload a clean HB!
This is bullshit!
 
Last edited:
How the hell can you say that you have removed v. .557 before 10:01 when I download .557 from the frontpage after a talk with Tony at around 15:40, where he wanted me to donwnload a clean HB!
This is bullshit!
it was removed, then we resolved the issue and right now you can download it and its clean.
 
it was removed, then we resolved the issue and right now you can download it and its clean.

So why talk about a .560?:
No it was .557 which was modified yesterday, the actual release build.

As soon as i saw that, i removed the modified .557, which caused the Server to pull back to .555

After that we made a new build, .560, scanned it and released it. Also scanned all our servers and found the intruder and eliminated it.

Just to clear things up:
Are there a .560 or only .557 thats been cleaned?
 
So why talk about a .560?:


Just to clear things up:
Are there a .560 or only .557 thats been cleaned?
heres a list of events that happend from the start.

infected 557 was pushed out.
we removed it and rolled back to build 555 <--everything is clean at this point
pushed out build 560 but it didnt work well.
build 560 was rolled back and replaced with a clean and stable build 557.

keep in mind that post is about a day old now so version numbers might not match. if you have any stored versions of 557 ether zip or extracted, then delete them and redownload the clean copies from the build server.
 
heres a list of events that happend from the start.

infected 557 was pushed out.
we removed it and rolled back to build 555 <--everything is clean at this point
pushed out build 560 but it didnt work well.
build 560 was rolled back and replaced with a clean and stable build 557.

keep in mind that post is about a day old now so version numbers might not match. if you have any stored versions of 557 ether zip or extracted, then delete them and redownload the clean copies from the build server.

Okay, thx.
Yeah I see that it's a day old, was just wondering why the version was the same as .557 and lower then .560.
I did download the version .557 yesterday at around 16:00 servertime.
 
Okay, thx.
Yeah I see that it's a day old, was just wondering why the version was the same as .557 and lower then .560.
I did download the version .557 yesterday at around 16:00 servertime.
like i said, 557 was much more stable then 560, thats why it was rolled back.
 
Lmao what is going on?

557 got infected > rolled back to clean 555.
Updates to 560 and then later on to 561.
THEN downgraded to 557 which works fine (also clean)
and now a 558 version which is now infected?

Im confused as fuck.
 
Back
Top