You need to run the scp command from the local machine, not on the remote. You don't need the ssh at all:

dragonmnl@local $ scp -P 2222 file.ext username@domain:~/ 

You also don't need the -r:

 -r      Recursively copy entire directories.  

If you are already logged into the remote machine and want to copy from your local, you need to make sure that your local machine is accessible via the internet and has ssh set up. I don't think this is what you are after but if it is, just run this from the remote:

username@domain $ scp dragonmnl@local:/path/to/file.ext ~/

You've botched your login shell's startup scripts, and that is bamboozling scp.

scp is starting a non-interactive SSH session and invoking a non-interactive login shell without a controlling terminal. But your shell's startup scripts are not checking for this case properly, and are doing the things that they do for interactive shells invoked with a controlling terminal. Indeed, those shells are blithely and incorrectly assuming that the terminal is a particular type of terminal.

All of that mysterious output is the result of commands in your shell's startup scripts outputting various OSC control sequences (␛[ and ␛/ being the ECMA-48 7-bit aliases for the OSC and ST control characters) and CSI control sequenes (␛] being the ECMA-48 7-bit alias for the CSI control character). These sequences are attempting to change colour mappings and affect terminal scrollback. They only work with a specific terminal emulator.

But the local end of your SSH connection is not something that mirrors all of this onto your local terminal (which, given that you are using MacOS, is unlikely to be that specific terminal emulator and more likely to be something like iTerm2, in any event). It is the local scp program, which is expecting to talk a specialized protocol over the SSH connection, that implements the file copying mechanism. All of the junk that your shell's startup scripts are erroneously spitting out even in non-interactive mode, is jumbling its communications.

Correct your faulty shell startup scripts to not attempt to do terminal stuff when they are invoked non-interactively or without a controlling terminal.

Further reading

• Why does bashrc check whether the current shell is interactive?
• SCP fails without error
• scp transfers file successfully into host machine but file won't show up
• Issues with scp if I use bashrc to open fish if present