Probably better to use a plain text or code editor to work on htaccess.
Would that not just create an identical htaccess file, with exactly the same suspicious redirect?
Yes, do make a back-up of your htaccess before modifying it, certainly if you are not confident in htaccess, so you will have that if you get it wrong.
Sam, we should not create multiple .htaccess file on the server at a given point of time.
So it’s recommended to first delete and then create a new file.
That was not my point. I was saying it is advisable to create a back-up copy of the htaccess before editing it, as a fall back in case you break anything in there. That back up does not necessarily have to be on the server, it could be a local copy, or re-named on the server.
It is actually quite OK to have multiple htaccess on the server, in different directories, as different directories may have different access permissions. For example some people keep include files above the root in a protected folder.
I prefer to edit and test locally, not on the server. Then only when it works as expected, upload to the server, overwriting the old version. If you delete, there will be a period where the file is missing.