[OFFICIAL] Tripwire event on 19-Feb-2016 02:23 UTC

[raphus]

We are aware of the Tripwire event that occurred on 19-Feb-2016.

If you are seeing this...

INFO CustomLogger (null) - Hearthbuddy is up to date!
INFO CustomLogger (null) - TRIPWIRE
INFO CustomLogger (null) - Please wait for an "[OFFICIAL] Tripwire event" announcement on the forums.
INFO CustomLogger (null) - https://www.thebuddyforum.com/hearthbuddy-forum/​

Here's what you need to know...

1. Don't Panic.
2. If you have other copies of Hearthbuddy running that are not disconnected by Tripwire (not possible unless you're doing naughty things), disconnect them as soon as possible.
3. This Tripwire event is unrelated to any previous Tripwire activation. All this means is the game client was updated in a fashion that requires immediate investigation

If this is your first Tripwire event:

You can find more information about Tripwire here:

BosslandGmbH:HelpDesk:What is Tripwire?​

​

What happens now?

We are looking into the situation, and updates will be provided as soon information becomes available.​

What can you do?

• Don't make new threads regarding the Tripwire event.
  We will leave [post=2160187]this thread[/post] open for Community discussions.
• Don't spread false information, and don't speculate on things you can't possibly know.
• Please be patient—these things take time.

 

[raphus]

Status Update

There seems to be a new update to warden that triggered the tripwire.

We will be sharing more information when necessary.

 

[raphus]

Status Update

Blizzard seems to be going aggressive with their spyware attempts. The new warden update is able to detect a wider range of applications that interacts with Diablo 3 and Hearthstone which includes Demonbuddy and Hearthbuddy.

We have about a 15 minute time window from around 19 Feb 02:08 UTC to 19 Feb 02:23 UTC for our users that logging in to the game and started Demonbuddy/Hearthbuddy to have their accounts flagged. You should be safe if you logged in to Diablo 3 or Hearthstone before 02:08 UTC or launched the bot after 02:23 UTC.

We are working on new builds and have no ETA as of now.

 

[raphus]

Status Update


We are hoping to push new builds in 12 hours.

 

[raphus]

Status Update

We have blocked the usage of old Demonbuddy and Hearthbuddy builds and will be pushing new builds that
will be as safe as before soon.

You might notice that our bots will be renaming themselves after they have launched. This is done for security
measures and shouldn't affect your daily usage. Bots will be leaving an auto updating shortcut (symlink) in the
folder which you can use as there was no renaming like before. We tried our best for this security measure to
not affect any reloggers or provide a bad experience in any form. Manually renaming the symlink or the exe
will not provide any extra protection and should be avoided.

Thank you all for your support and happy botting.

 

[raphus]

New Release available

We're somewhat delinquent in this announcement, as the release has been available for several hours. The update got lost in the shuffle—apologies. The new release is here:

Bot Updates​

All time-limited keys have been extended to compensate for the downtime.


Things to know:

• You should ONLY be using a Hearthbuddy release of '.233 or later.
  It is NOT SAFE to use previous versions of Hearthbuddy.
  
  Bot Updates​
  
  Please do a fresh install (into a NEW directory) if you don't get prompted for an update, or have problems with Hearthbuddy after doing an update.
  
  
  
• You should not be using any other tools (or bots) that attach to Hearthbuddy.
  This includes tools that "don't inject" or are "pixel-based". All such tools are a problem, unless you have gotten the 'all clear' from their author. The spyware scans of 19-Feb-2016 are more encompassing than [post=2154623]those detected on 9-Feb-2016[/post]. So, if you previously got an 'all clear', you need to check again.
  
  
  
• Hearthlogger (Hearthbuddy) and YAR (Demonbuddy) are safe to use.
  Reloggers may fail to launch and just 'monitor' on their first try. This can be worked around by doing a single manual start on first use.
  
  
  
• If you have problems, please open your own thread in the Support forum.
  Please don't piggyback on someone else's Support thread, and don't forget to attach your log that illustrates the problem you have.
  
  Ref: [post=378165][Guide] How to attach your log[/post]​

Is it safe to use?

Bossland GmbH does not allow Buddy bots to run, if it feels they are unsafe. Simple as that. This has always been true. More info here:

BosslandGmbH:HelpDesk:Is Botting Safe?​