Hi everyone. This is 2nd episode of my Steemit Bot series.
While reading through the feed, I saw there are lots of people who got hacked due to mistakes in transfer
So this motivated me to make a new bot.
Generally, this kind of things happen because they habitually wrote their very own ‘owner key’ into the memo slot.
Most sites have an input box in ID,PW order. So they just copy and paste, not knowing they made a huge mistake.
Every memo would be opened to public because It’s a Blockchain.
There are some hacking bots abusing this feature.
They keep detecting each and every transaction till some value that seems to be owner key. Then they log in and take all your SBD and Steem.
So I borrowed this concept too to fight against them.
My bot also detects Owner key among transactions.
Oh don’t be afraid of! Calm down
Once owner key is detected, My bot would try to log in. If login was successful,
then it would immediately change password.
Then it would comment or reply on post of hacked account that ‘It is hacked. So try to restore your account’.
Those evil hacking bots are still looking for scapegoats. It would take less than 10 seconds to hack your account since the data of owner key is on the Blockchain.
So I designed my bot with offbeat sense.
There are 14 bots with different nodes. No one shares node with any other bots.
It is because to prevent receiving transaction data later than Evil bots. So it doesn’t matter if one or two nodes became slow.
Once the owner key is detected, hacked account and owner key would be sent to another bot which only controls anti-hacking methods. ; different one from the above 14 bots.
This anti-hacking bot would send requests through every node with different thread. If the password change was successful, it would notice that the account is hacked and recommend to restore.
If there are no post at all, only password would be changed.
Even if my angel bots successfully changed password and halted hacking bots, You MUST contact Steemit to restore your own account.
I can never know whether you’re the only owner or not. So I can’t help you directly.
For instance, hacking bots got faster than my bots. Then there is no more solutions.
But, For now, to prevent this kind of problem, I tried to make each process as fast as possible. I divided threads as much as possible and commanded them to send datas and infos ASAP to the ‘Anti-hacking bot’.
It seems that there are no API related to unconfirmed transcations. If I could launch a node, I would try to. So that I could move 3 seconds faster that evil ones.
The best way is Not To Make Any Mistake!
And also keep your SBD and Steem separately. Never let anyone know your key.
There are more than 15 evil hacking bots. Once the key was leaked, unhappy event would occur in 10~20 seconds. So get Alarmed and Don’t forget to check your memo box always.
If Active key was leaked, password won’t be changed. I tried to cover it by changing all the balances to Steem Power and noticing the leakage.
this is the best i can do
Among the reader, If any delegate asks me to provide Source Code, I would happily give it to him/her.
The more people run 'Angel', the more effective it is.
https://steemit.com/kr/@otac/steemit-alarm-bot
Also plz check my ‘Steemit Push Alarm Bot’ =)
--- 이 글을 읽는 한국인 여러분께 ---
외국에 소개하기 위함입니다 이미 한글 게시글로는 업로드 해두었습니다
본의아니게 글을 나누게 되어 불편을 드려 죄송합니다.
