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 bytecode manipulation in order to prevent the modification of parameters within the Filter and Condition classes themselves (thanks @wastedbro)


      Fix NPE caused by non-null value in GE API (thanks @erickho123)


      Add and fix equals methods for api2007.types (thanks @JoeDezzy1)


      Modify Mouse#leaveGame to make the mouse leave the game from top, left, right, or bottom (thanks @erickho123)


      Add Entrana area to Ships API (thanks @erickho123)


      Fix raid prayers index/settings in Prayer API (thanks @erickho123)



      Upcoming updates:

      Break handler bug fix


      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
      • 27 replies
    • This update will:

      Implement better canvas locking/synchronization mechanism


      Fix small Login API bug


      Remove the requirement for xbooting Java classes


      Use ExecutorService to perform canvas work in parallel


      Add "Account Management" game tab to GameTab API (thanks @Encoded)


      Fix NPCChat#getMessage (thanks @Encoded )


      Fix NPCChat#selectOption (thanks @Encoded )


      Fix Banking API after today's update (thanks @Encoded )


      Fix in-game world hopper after today's update (thanks @Encoded )



      Upcoming updates:

      Break handler bug fix


      Improved CLI support


      Much more



      Note: If you are using LG, please restart both the RS client and TRiBot
        • Like
      • 38 replies
    • This release includes:

      Fix updater bug which was causing a bunch of issues


      TRiBot will no longer require manual hook fixes every time the RS client updates - the updater has been fully patched for objects


      Hooked login fields


      Improved the login bot


      Ability to recognize the banned/locked messages again


      Ability to read the current input for username and password fields


      If the username or password is already entered correctly, it won't be erased


      If only part of the username or password is already entered correctly, it won't be erased. The login bot will fill in what's missing.


      If there are a few invalid characters after a valid substring of your username/password, only (approximately) those invalid characters will be erased. The login bot will then proceed to fill in the missing characters.





      Coming soon:

      Skull icon fix


      Improve screen rate and responsiveness of the RS client (both regular client and LG)


      Much more
      • 33 replies
    • This release includes:

      Fix shift clicking option selecting


      Fix high paint delay settings saving


      Update prayer IDs for the quick select menu


      Remove RS3 support


      Fix hooks



      RS3 Support Removed

      The RS3 client hasn't been updated since our Old-School version of TRiBot was released, as many of you may have noticed. Keeping all of the RS3 code in the client made the client as a whole harder to maintain, larger, slower, and messier. As hardly anyone still uses the RS3 client, and since the RS3 API was hardly functioning, we made the decision to completely remove it from TRiBot.

      For the average user, this means that the client will be smaller, cleaner, and faster. Future updates will also take less work meaning there will be more frequent updates.

      If you were one of the few users still using the RS3 client, we apologize for the inconvenience. No future support for RS3 is planned. There are many other botting clients which has support for RS3, so we recommend finding an alternative if you wish to continue botting on RS3.
      • 25 replies
    • Please welcome our new developers, @JoeDezzy1, @erickho123, @Encoded, and @wastedbro.

      These members will be responsible for working on, maintaining, and improving TRiBot.

      This means that bug fixes and improvements will now come at a much faster pace! We're committed to providing users with the best botting experience possible!
      • 30 replies
  • Recently Browsing   0 members

    No registered users viewing this page.

×