I was working with ethereum using: - solcjs

And when I checked my wallet in the kovan node, the balance has been transferred to 0x093a0ed738b65ed34f2a37a2d44c5e3cd0d0dd45 on this transaction https://kovan.etherscan.io/tx/0xf33a3a43b7a13dae0d5d83027ec642a6fd383eafe3d0c5f5c6cedb3580ddb59a?

The transfer happened pretty much when I do a curl call to personal_unlockAccount. Does this transfer because I unlock my account? and there is someone who scanned and auto transfer to 0x093a0ed738b65ed34f2a37a2d44c5e3cd0d0dd45? The wallet seems to have a lot of KETH on the wallet.

Or this might happen because of the third-party tools I'm using mentioned above?

  • According to etherscan, it's an externally-owned account (i.e., not a contract account), to which you have sent 0.000011877202619047 Ether (11,877.202619047 Gwei). – goodvibration Mar 24 '20 at 12:16
  • Just open the transaction link provided in your question, and then click Click to see more. You'll see that exactly 21000 gas units were spent, which means that this transaction is ether-transfer to an externally-owned account. – goodvibration Mar 24 '20 at 12:17
  • To answer your other question - it depends on where you send the curl to. If it happens pretty much after you do that curl, then it makes sense that it's either the entity on the other side who's making use of your credentials, or perhaps your own script does that (I'm assuming here that you haven't wrote it yourself). – goodvibration Mar 24 '20 at 12:19
  • Yes, that is what I'm afraid, the script that I didn't write myself, and I listed them all on my question. and they seemed to be fine.. – bbnn Mar 24 '20 at 12:22
  • Hang on a second - public no firewall kovan node??? Does it actually make any sense to you to unlock your personal account on a public node??? – goodvibration Mar 24 '20 at 12:22

I ran into this recently, too. This same address kept draining my account balance and I thought they must have gained access to my server because I was sure I'd closed down the firewall. Problem for me was that I hadn't realized that I still had my firewall open on the RPC port, and the easy fix was to close that port :).

This is just for anyone else who might come across this on google.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.