No, it's impossible to control someone else's address without its private key.
Bitcoin isn't designed to be controlled by a central authority.

However, if you can track it and found out that it's in a centralized service like an Exchange or Gambling site,
then it's possible to contact their support to inform them about the hacking incident (with enough proof)
in order for them to freeze the hacker's account.
But if it's in a non-custodial wallet like Bitcoin Core, Electrum, blockchain.com (except trading wallet), etc., there's nothing you can do.

Is this the error that you're getting?:

If it is, it's not Bitcoin Core's version at fault.
The passphrase you've entered is correct but the wallet.dat may have corrupted or tampered data in it.

"Brainwallet" is a different thing, it's basically a SHA-256 sum of the "passphrase" that will be used as a private key.
Based from your reply, it can not be a Brainwallet.

Random picked words from the old wordlist works because there's currently no "seed version system" before v2 (link).

I've tested with v1.8.1 and it accepts 12+ words when restoring a wallet from the old list while the latest version only takes 12 or 24.

If you're certain of the seed phrase and the words all belong to the old wordlist:
Try to restore it in v1.8-1.9.8 that can be downloaded from the "Previous releases" link in the official site.
When prompted with connection errors, cancel everything until the wallet is created.
Then open the wallet file "electrum.dat" using the latest version 4.0.5 (File->Open->Browse to the location) to sync it to the network and to see your balance.

If you're positive that it's the exact URL that you've been using, then it's legitimate and probably won't hack your balance.
Here's their official Bitcointalk thread: https://bitcointalk.org/index.php?topic=320959.0.

For the hacker, he also got the email password so it's pretty easy to withdraw from freebitco(in) if you didn't set 2FA on.

Passphrase?
Do you mean "seed phrase"? Which is the 12-words used to recover the wallet since you've mentioned "wordlist".
AFAIK, it should work in the new version and it will be recognized as "old" when you try to restore it.
Speaking of wordlist, here's the old wordlist (before v2): https://github.com/spesmilo/electrum/blob/1.9.8/lib/mnemonic.py
Check if your passphrase's words are in it.

You might be using a "Brainwallet" instead of Electrum seed phrase because of the term "passphrase" for seed phrase.

You can try to disable Windows Update in "Search->Edit Group Policy"
Under 'Computer Configuration', expand "Administrative Templates->Windows Components->Windows Update".
On the right pane, set 'Configure Automatic Updates' from 'Not configured' to "Disabled".

Using that setting, my Windows10 Rig has been at version 1709 for 5months and never updated.
I don't know if will actually work since I've deferred windows updates in the settings for 365days.
But this is what the description says:

Some features are still being automatically updated though.

And to disable automatic drivers update, enable the policy: "Do not include drivers with Windows Updates", as written in its description.
You might want to check the other policies in there too.

According to the OP and Claymore's last few posts:

This was the transaction: 6dd153b11b3dbd65543768c8760b435fe92dabf0bfa896e532b06b3b5c2e0aab
Looks like he have used "increase fee" since the outputs were the same.

@JH16 that's not an issue by the way.

Usually, it takes from 1day to two weeks (or more) depending on the PC.
It's mostly based from your internet speed next is your machine's specs.
To speed things up, I'd suggest you to increase the dbcache to at least half of your RAM.
The option is in "Settings->Options->Size of Database Cache".

For the fee, you can time it right when there are a few transactions in the network, you can use this site to check if the average fee/mempool size is low:
https://jochen-hoenicke.de/queue/#0,2h

You could get to know what happened but it's impossible to "resolve" it (if it's about getting back the funds).

Start by looking for some archived conversation between you and your "friend" and check for the address that he's given you.
Compare the address to the transaction output's address, make sure to check all of the characters because some clipboard hijacking malware/virus has the capability to create vanity address that's similar to the target.

That is weird, blockchain.com's withdrawal can't be a "batched withdrawal" unless you own the input which previously had 60BTC balance.
77aa973b985badd0e915b9c72b9c5da396013ab9bb06c4b75564fdb2f2f0041c looks like a withdrawal from an exchange, casino or a custodial wallet.

It may look like that if it's a transaction made by blockchain to send your 'Trading wallet' funds to one of your 'normal' wallets.
In that case, 14cac8EzqBKs8Wrwt5ZXippow8ZCmtYfzb can't be an external bitcoin address.
Also in that case, aba21510d34335a1f9d5c6137fff8718133ca86f487b12e6ded8a9e0f203b133 may be the transaction that spent all of your wallet's balance.

Was it a different "blockchain" wallet?
Or are you certain of what happened (because it's been 8 months since based from the timestamp)?

You're already using a non-encrypted wallet.dat,
it's basically a collection of unencrypted private keys that're ready to be taken anytime if your machine isn't secured.

In terms of "danger", you are already at the red zone.

Risks and to do's:

• The basics: do not share the wallet file, private key(s); "hdseed" and "extended private masterkey" from the wallet dump file.
• If you're planning to sync Bitcoin core, at least encrypt your wallet.dat and make another backup after; there will be a warning about it if you try to encrypt the wallet.
• Keep the old backup safe in an offline storage for insurance
• Make sure to verify the signature of the wallet that you're going to use before using or importing anything in it.

It's already showing the estimated fee rate as sat/kvB like in your example above, it's 3147sat/kvB. (electrum/commands.py)

You mean BTC/kB, or better BTC/kvB?
Like 0.003 BTC/kvByte not 0.003 sat/kvByte as shown above which is totally way below a "standard transaction's" fee rate. (should be 0.00003BTC/kvB for 3000sat/kvB or 3sat/vB)

Anyways, rounding it may introduce inaccuracy when it comes with huge transaction sizes, but it's fine in most cases.

If the error you're getting is what hosseinimr93 has said (quote below),
Then there should be no passphrase set because you'll get Error: Please enter the wallet passphrase with walletpassphrase first. (code -13)
with dumpprivkey whether the address is correct or not.

Aside from post number 2's reply.
it's also the virtual byte if you mean "fee rate" that most miners will be using for prioritization (except miners w/ non-SegWit nodes).

Yes it does, as per the release note:


Op had posted this on November 16, 2 days before version 4.0.5 release.

I have tried to broadcast my sample transaction few minutes ago and it's working for that transaction.
Here's the link: https://live.blockcypher.com/btc/tx/cedecdb6413f8f69489ec201b8cd03de08d92e8776b0a61e6a3ff9ef44f21614/

But I'm getting the same error when I tried with leventturksoy's 'normal fee raw transaction'.

No one has reported the issue but there are a lot of automatic bug reports: https://github.com/spesmilo/electrum/issues/6356
It is the same error displayed in your third screenshot's "Traceback".

And it seems like not confined to macOS since there are reports from Windows and Linux as well.

---

-update-
It will be fixed in the next release.

IMO 2010 was a bit early for web wallets and paper wallet generators.
An early adopter might know some.

Your best bet is to find a "wallet.dat" file like suggested in post number 2.
Or an exported WIF private key which is a 51-character string (random-case/base58check) that starts with '5'.
eg: 5JQpcp6Thh7QR4mNxfQFgsfKVTkzoK9CxdBySQRtgpox5g8RwLJ

Will you reinstall the older version?
Depending on your previous version, it may not be able to read the current wallet file.

If you'll reinstall 4.0.x+, there will be no problem; but if you'll reinstall v3.3.8 and below, you will be needing to restore using your seed phrase because the upgraded wallet file can't be read by those older versions.