What happened
An input may be filled by the website, browser autofill, a password manager, or your paste. A complete value visible on screen is not proof that it is the current recipient stored by the server. Identify where the text came from and whether the form has unsaved changes. The distinction matters especially after regenerating a token while the browser still remembers an older address.
What to check
Load the profile freshly and read the saved value. If autofill inserts an unwanted address, replace it with the current source copied from your own Steam account. Inspect the field immediately before saving. Save deliberately, reload, and compare the persisted value with the intended source. Request verification afterward. Do not export password-manager records or authenticated browser data simply to explain that a form suggestion changed.
Worked example
For example, you paste a new link, but focusing the field again causes the browser to insert yesterday’s suggestion. The form still looks complete and ownership may be unchanged, yet its token is stale. Comparing the field before save and after reload reveals the replacement. If a fresh reload returns the old value without any browser substitution, report persistence separately rather than blaming autofill automatically.
Result and next step
A completed repair leaves the intended current address in a fresh profile view and a verification result for that persisted value. Record browser name and the exact moment the suggestion appears when reporting the issue. Keep the address private. Read Steam account security advice and CASECS2 workflow. An unsaved visual edit, a successful save, and a live check describe different states; none should silently replace the evidence from another.