Whenever I use the Docs tab and type an asterisk in a codespan, like `*`, and then make the editor lose focus, a backslash is automatically added before it, making `\*`. This symptom is repeating: it becomes `\\*`, `\\\*` and so on.
I am using Postman v11.84.2, the latest version at this moment, on Windows 11 25H2.
Welcome to the Postman Community! 
It looks like it applying the syntax for a multiple line comment but it is weird behaviour. Is it blocking you from doing something specific?
If you needed it, you could use the codeblock or the Markdown editor as a workaround?
Currently I cannot share regexes containing asterisks, for instance ^[A-Za-z]{3}\*$, so I am using a workaround excluding the asterisk out of the codespan like ^[A-Za-z]{3}\*$ (Markdown: `^[A-Za-z]{3}\`\*`$`).
The same thing happens when switching from Postman editor to Markdown editor, but not vice versa.
After a full-week off for the Lunar New Year, I got an update to v11.85.1-260219-0947 and checked this issue again.
First I thought this was solved so that I wrote a reply here this morning it was solved, but deleted it just a minute ago after finding it was not. Further researches are following:
* becomes \*.** retains itself.*** becomes **\*.**** retains itself.***** becomes \*.****** becomes **, and so on.It seems to be related to auto-formatting because I spotted some sequences changing into something like _\_ (Though I cannot remember what was the original string) during this test.
I can second this. I can use the Markdown editor to change \*Hello world\* to *Hello world*) but as soon as I view the Postman collection normally again (i.e. come out of the Markdown editor) it changes back to \*Hello world\*. Plus sometimes if I click out of the collection and then back into it again I end up with \\*Hello world\\*, then \\\*Hello world\\\*, and so on.
Basically you can’t include any * inside a single-line or multi-line code block without Postman messing it up.
PS: Running the latest version of the desktop application right now (v10.12.6) but the bug occurs in the the online editor too.