Since our last update post 3 weeks ago, a lot of things happened. In this post, we are going to talk about them.
On July 4th, NobleBot got its first active private key and acted as accordingly by transferring liquid funds to victim's savings account. There were 2 cases of this and in both cases, NobleBot was able to help with SBD but failed to transfer STEEM (NobleBot was beaten by another bot).
To react to not able to transfer STEEM to savings, NobleBot's code was updated. It performed well in testing but not tested in real life situation. So, we are hoping it would as expected. We'll post more update on this in future posts.
We saw that many victims' account was updated with ACTIVE, POSTING, and OWNER authorities to the hacker account. This gives the hacker to control even if the victim changes the password. Hackers also change the victim's vesting withdrawal routes.
NobleBot brought a tool to help victims reset their account. This tool requires the victim's active private key but will be updated to SteemConnect when they will support the removal of owner and active authorities.
The NobleBot has been working with 
If NobleBot gets your key and changed it, you'll be notified via comment or transfer memo or both by NobleBot (
| Keys Found | Success Rate | Accounts Recovered | SBD Saved | STEEM Saved |
|---|---|---|---|---|
| 21 | 42.9% | 60% | 95.38 | 2.002 |
Keys Found - Total Master and Active keys detected
Success - NobleBot was able to help
Account Recovered - Percentage of accounts recovered by the original owner
SBD Saved - Total SBD saved by NobleBot
STEEM Saved - Total STEEM saved by NobleBot
In case of a memo and posting private key, NobleBot warns the victim's via memo and comment respectively.
The development of this bot is kindly supported by
Cover photo background and NobleBot logo credit goes to Pixabay.com
