raphus
Well-Known Member
- Joined
- Jun 17, 2010
- Messages
- 2,094
Honorbuddy was recently hit with another banwave.
We have spent the last two days trying to figure out how Honorbuddy was detected.
After the May banwave the Tripwire service was made a lot more aggressive to catch
any detection methods that it might have missed. However, having reviewed the server
logs, it was discovered that Tripwire service was not running properly after an update
that took place about a month ago which nullified all the new heuristics.
We do NOT know for sure what caused the banwave, but we strongly believe the tripwire
service would have been able to catch the detection that took place if it was working
properly.
Words cannot express how sorry we are for this mistake, but we are truly sorry. We
take your account security very seriously and strive to do everything possible so
that this exact situation does not occur.
We now plan for the service to run for a while with these checks configured correctly
and see what it shows. In the meantime we will update you when we are ready to re-open
auth and to do a test release. Please be aware that this release will still be considered
'unsafe' to use and, like always, should not be used on accounts you cannot afford to lose.
Again, we sincerely apologize for this massive mistake.
This thread will remain open for discussions.
We have spent the last two days trying to figure out how Honorbuddy was detected.
After the May banwave the Tripwire service was made a lot more aggressive to catch
any detection methods that it might have missed. However, having reviewed the server
logs, it was discovered that Tripwire service was not running properly after an update
that took place about a month ago which nullified all the new heuristics.
We do NOT know for sure what caused the banwave, but we strongly believe the tripwire
service would have been able to catch the detection that took place if it was working
properly.
Words cannot express how sorry we are for this mistake, but we are truly sorry. We
take your account security very seriously and strive to do everything possible so
that this exact situation does not occur.
We now plan for the service to run for a while with these checks configured correctly
and see what it shows. In the meantime we will update you when we are ready to re-open
auth and to do a test release. Please be aware that this release will still be considered
'unsafe' to use and, like always, should not be used on accounts you cannot afford to lose.
Again, we sincerely apologize for this massive mistake.
This thread will remain open for discussions.
Last edited: