Read what the guy himself says about it: https://www.malwaretech.com/2017/05/how-to-accidentally-stop-a-global-cyber-attacks.html

Basically, he thinks that it was just a very poorly written anti-sandboxing thing.

Unfortunately because you are using blockchain.info's wallet, you won't be able to do anything except ask a miner for help and wait.

Please read https://bitcointalk.org/index.php?topic=1914800.0

The absolute value of your transaction fee is completely meaningless (especially the fiat values). What matters is the fee rate in sat/byte.

Your first transaction has a fee rate of 44 sat/byte. Your second has a fee rate of 10 sat/byte. Your third transaction has a fee rate of 402 sat/byte. The first two transactions have a fee rate that is much too low. The current recommended fee rate is 260 sat/byte according to https://bitcoinfees.21.co/.

Furthermore, your second transaction spends from your first transaction, so it cannot confirm until the first one does as well. Your third transaction spends from the first and second transaction, so it cannot confirm until both of those do too.

Please read https://bitcointalk.org/index.php?topic=1802212.0 for what you can do about your transactions.

What wallet software are you using?

Did you, at some several days or weeks ago, attempt to make three transactions that have the same values sent as these three transactions? If you did, did those three transactions not confirm and eventually the balance went back to you and it looked like the transactions had been "returned"? If so, what happened then was that a miner still had your transactions and eventually included them into a block.

You should also stop using blockchain.info's wallet as it is well known that their wallet is poorly written (especially the fee estimation and coin selection stuff) and has had security issues in the past.

If you copy and pasted directly from the examples on that site, then it is wrong. There's something wrong with the quotation marks that are used there. Type it out manually, don't copy and paste.

Also, bitcoinarmory.com is not our website. The website is https://btcarmory.com/

Please post the transaction id of the transaction.

The issue is likely due to a low transaction fee or spending from other unconfirmed inputs. Given that you are using blockchain.info's crap software, both possibilities are extremely likely to have happened.

Please read https://bitcointalk.org/index.php?topic=1914800.0

Bitcoin Core's databases (LevelDB) doesn't work with network shares. You won't be able to have the datadir on a NAS.

97 sat/byte and 101 sat/byte is much too low. The current recommended transaction fee rate is 240 sat/byte according to https://bitcoinfees.21.co/.

Can you also post the transaction ids of your unconfirmed transactions?

What wallet software are you using?

Please read https://bitcointalk.org/index.php?topic=1802212.0 for what you can do about your transactions.

Please read https://bitcointalk.org/index.php?topic=1914800.0

Unfortunately there is not much that you can do except ask miners for help and wait.

Probably not, but predicting when a transaction will confirm is incredibly hard. Unfortunately for you, the majority of transactions are in the 120 sat/byte range (because a lot of people use blockchain.info's shit software) and they can't all be confirmed at the same time.

120 sat/byte is not sufficient. The current recommended transaction fee is 240 sat/byte according to https://bitcoinfees.21.co/.

Read https://bitcointalk.org/index.php?topic=1802212.0 for what you can do about your transaction.

What wallet software are you using?

Please post the transaction id of your transaction. The absolute value of the fee is completely meaningless as miners do not use that to determine which transactions to accept.

Also, read https://bitcointalk.org/index.php?topic=1914800.0. Since you are using blockchain.info's wallet, there is not much that can be done.

You paid a low transaction fee, only 120 sat/byte. The current recommended transaction fee is 240 sat/byte according to https://bitcoinfees.21.co/.

Read https://bitcointalk.org/index.php?topic=1802212.0 for what you can do about your transaction.

What wallet software are you using?

Having the public key saves on computation time since it is hashed and compared first before doing the more expensive signature validation operations. Otherwise attackers could just put invalid signatures which first have to go through expensive signature operations to get the public key, and then compare the public key last. That could potentially be a DoS attack vector.

Ok, I have pushed your transaction, and I see why it is delayed and has poor propagation.

Your transaction spends from two unconfirmed transactions: https://blockchain.info/tx/a9d008e6a80806670f8c3d0f3404e87ff19f81e71ef9601fc7c4fd6ccf28f48b and https://blockchain.info/tx/81890605cf42773aefa766964862973ded4d8746f2a7d2656412c064c7d68d37. Your transaction cannot confirm until these two transactions confirm as well. However, both of these transactions only pay a transaction fee of 10 sat/byte, which is way less than the 270 sat/byte fee rate recommended by https://bitcoinfees.21.co/. Since the fee rate of those two transactions is so low, most nodes have removed them from their mempools, and because of that, they cannot accept your transaction since they don't have these two unconfirmed transactions.

Read https://bitcointalk.org/index.php?topic=1802212.0 for what you can do about these three unconfirmed transactions. Note that doing anything to just your high fee unconfirmed transaction is not going to help, you need to get the other two low fee unconfirmed transactions to confirm too, otherwise yours will not be able to confirm.

There's your first problem. Read https://bitcointalk.org/index.php?topic=1914800.0

Unfortunately, because you use blockchain.info's wallet, there is not much you can do except for asking a miner for help and waiting.

It is still not enough. Blockchain.info's fee estimation is horrible so what it recommends is definitely not enough.

In the transactions list, right click the transaction and choose "Copy Raw Transaction". Then paste what was copied into a post here. That is the raw hex of the transaction itself and posting it will allow people here to rebroadcast the transaction for you so that the network actually sees it. The problem is likely due to poor propagation of the transaction as I am unable to find it both on block explorers and on my own node.

What wallet software did you use to make this transaction?

The transaction fee is fairly low, only 114 sat/byte. The current recommended transaction fee is 270 sat/byte according to https://bitcoinfees.21.co/.

Read https://bitcointalk.org/index.php?topic=1802212.0 for what you can do about this transaction.

Please post the transaction id of the transaction.

You cannot change it after the fact. Since the transaction has already been broadcast, you cannot change it to be RBF enabled. That can only be done when creating the transaction, before it is signed and broadcast. Your transaction is not RBF enabled.

I have never heard of a fw2 file extension. All the major wallets that I know of use .dat, .wallet., or .key as their wallet file file extensions.