[OFFICIAL] Tripwire event on 9-Feb-2016 21:52 UTC

[raphus]

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

If you are seeing this...

INFO MainWindow TRIPWIRE
WARN MainWindow Shutting down in 20 seconds!​

Here's what you need to know...

1. Don't Panic.
2. If you have other copies of Demonbuddy 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.
• 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

Tripwire has sensed a disturbance in Diablo and Hearthstone spyware (a.k.a Warden). Auth servers will remained closed for Demonbuddy and Hearthbuddy until we get more information.

We will keep you folks updated.

 

[raphus]

Status Update

Tripwire event has been triggered by a new warden module being pushed by Blizzard. That means Blizzard is trying something new to catch bots or other third party tools.

While we can not give an ETA, at a minimum, it would be reasonable to expect a 12-48 hours downtime from now on.

Thank you for your understanding.

 

[raphus]

Status Update

The new warden scan is capable of detecting any program that is interfering with Diablo 3 and/or Hearthstone. We strongly
recommend not to use any Diablo 3 or Hearthstone tools until they are updated.

Accounts that logged in to Diablo 3 or Hearthstone after 09 Feb 2016 21:05 UTC until the tripwire event (21:37 UTC), and launched
Demonbuddy/Hearthbuddy within that time window might have been flagged by the new scan. We do not suspect accounts that were
already logged in before then to be flagged.

Summarising the above, we do not expect your account to be flagged if you:

• were logged in to Diablo 3 or Hearthstone before 21:05 UTC
• were logged in to Diablo 3 or Hearthstone after 21:05 UTC, but haven't launched Demonbuddy/Hearthbuddy until the tripwire event

Unfortunately, we still don't have any ETA for new releases and auths to be reopen.

 

[raphus]

Yet another clarification;

Your account is safe if either:

• you already had Demonbuddy or Hearthbuddy running before 21:05 UTC and the bot shut down at 21:37 UTC due to tripwire.
• you tried to launch Demonbuddy or Hearthbuddy after 21:37 UTC and received Tripwire message.

Your account might be flagged if:

• you launched Diablo 3 or Hearthstone and launched Demonbuddy or Hearthbuddy after 21:05 UTC and before 21:37 UTC

I hope this makes it clear for everybody

 

[raphus]

Status Update

We are about to open auths and release new builds while blocking the usage of old ones for Demonbuddy and
Hearthbuddy. Before we do so, we would like to share the findings about the new warden scan with the community.


The new detection method checks for all running applications on your computer and processes the ones that interact
with Diablo 3 or Hearthstone. This means that bots and tools that don't use injection may also be detected. We went
ahead and checked if Turbo Hud and Ros-bot can be detected with the new scan for the sake of the Diablo 3 botting
community.


Unfortunately, the tests for both programs showed that they are both detected by the new scan and it is up to
Blizzard to ban accounts using Ros-bot or Turbo Hud. We are sure that Blizzard knows if you are using them or not
since 21:05 UTC last night.


The new warden scan is still occasionally running, and continues to detect these two tools and possibly more.
We strongly suggest our users to not use any tools for Diablo 3 and Hearthstone until it is made clear by their
developers that the tool is not detected. Developers of other tools should feel free to contact us for more information.


Demonbuddy and Hearthbuddy will be as safe as before with the new releases.

 

[raphus]

We are aware of crashes, and working on new builds

We are aware of the crashes being caused by the new versions of the bots and working on a fix right now.

New builds will be pushed asap.

 

[raphus]

New build available

• New builds have been pushed that should fix crashes..
  You should only be using a Demonbuddy release of '.453 or later
  
  Bot Updates​
  Please do a fresh install if you don't get prompt for an update.
  
  
  
• You should not be using any other tools (or bots) that attach to Diablo3.
  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.
  
  Hearthlogger (Hearthbuddy) and YAR (Demonbuddy) are safe to 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]​

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


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?​