Jump to content
Usa

Account Security

Recommended Posts

Hello TRiBotters, this is a PSA regarding Account Security.
 
Recently I've seen a growing number of Account Security issues leading to more Account Recovery requests.
 
While your security and anonymity at TRiBot is taken very seriously, some related sites have had issues protecting your account information. As you may already know, various black market, private servers, and other clients have had their databases compromised and dumped. 
 
What this means for you is if you are using the same username and password across all sites, your TRiBot account may be at risk.
 


What we advise,

  • Use a unique password at TRiBot different from all other sites (longer, more symbols, more characters the better)
  • Never share your account details or type them anywhere else but at TRiBot forums or the client.
  • Enable Google Authenticator for extra account security.

 


How do you use Google Authenticator?



If you are aware that you are using the same password across all sites, we recommend you change your password at TRiBot to something unique to keep your account safe.
 
Thanks and happy botting!
 
TRiBot Staff

  • Like 6

Share this post


Link to post
Share on other sites

never used google auth how often do you have to use the app ? each log in ? or 1 time a IP ?

 

  • Like 1

Share this post


Link to post
Share on other sites

Secure your account folks! i about lost my mind yesterday because one of my farm accounts got "hacked"  lost about 50m 

 

 

now the loss of the gp wasnt a big deal what really got me is how in gods name someone got my pass/user ! 

 

PS.

I work in IT and im studying IT security so most of my stuff uses a 16 character password lower upper case, anti virus and any registry changes to be prompted. (just basic stuff  straight out of Da book)((key-loggers are soo 2002))

 

 

After about 2 hours of research and and 3 hours of crying to YoHoJo trying to blame Tribot i figured out some prick from Taiwan managed to gain access to my old fb account, found out my old email account recovered it and then found my old password sheet in a draft folder (i know never write down passwords but this sheet had 30+ users/ pass most obsolete) anyway  so the prick gained access to one account and cleaned it.

 

 

 

To summarize, in this day and age you really arent safe, take the extra step and  follow good habits such as resetting your password monthly for all systems  and if your not using an old email or FB or twitter to simply delete it. Otherwise they may take a whole lot more than 50mill. To me thats a small price to pay for a good reminder. 

Share this post


Link to post
Share on other sites

That's not true.

 

Actually you're partially right. I spoke to said person about this. I was wrong about your db being dumped. The bot was "cracked" in the past by someone who had Spoofed the SSL server and patched GetAddrInfo during runtime for any authentication requests to come to said server.

 

I hope the procedure for the bot has been improved upon since.....

Edited by True_Mako

Share this post


Link to post
Share on other sites

Thank you for a good reminder, one easily gets lazy after a couple of years :P used to be so paranoid changing passwords every week but as the years passed by it started taking longer and longer in between. Well now I'm updated nearly every online account :-)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Our picks

    • This release will:

      Fix key event handling issue


      Fix other event handling issue


      Fix RSServer hook


      Update world hopper to have it use OCR, thanks to Todd


      Use proper disposal of old Graphics objects


      Reformat code


      Rearrange code


      Organize code imports


      Apply around 8000 automated code refactorings


      Make preparations for Java 9


      Fix 11 various bugs


      Add more reliable debugging support


      Fix mouseEntered/Exited event dispatching bug


      Fix minimap walking bug where it opens the map


      Fix broken hooks for today's game update
        • Thanks
        • Like
      • 55 replies
    • This update will:

      Fix GE inventory item positioning bug


      Fix broken object hooks
        • Like
      • 27 replies
    • This release will:

      Fix some ClosedChannelException bug


      Fix bug in RSObject#getAllTiles


      Add game tab support for "Kourend Favour"
        • Like
      • 15 replies
    • This release will:

      Fix Settings UI placement bug


      Fix game object location bug


      Fix small layout bug making the client shift up and down


      Fix client crashing bug where loading the client with a small display area will cause the client to crash


      Fix annoying Linux bug relating to painting events and peers


      Fix settings saving bug where settings are saved to disk more often than they should


      Fix RSInterface#isBeingDrawn bug affecting a limited amount of people


      Drop Java 1.7 bytecode version for 1.8


      Important: Since the downloadable RS client uses Java 7, it will no longer be compatible with Looking Glass. To make up for this, we will add support for using other clients such as RuneLite (at a later date).


      This change was necessary to allow us to use Java 8 syntax. It also paves the way for Java 9/10/11 support.
        • Like
      • 40 replies
    • This update will:

      Fix the RSMenuNode bug which also fixes the bug with bank opening


      Fix the incorrect object positions bug


      Fix and re-enable the LG Objects API Accelerator


      Fix the RSObject#getAllTiles bug
        • Like
      • 22 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×