Unfamiliar login notice
Compare its time and device with your own activity; follow the relevant security process if they do not match.
A unique password helps prevent a problem in one account from spreading to another. Sharing it defeats that separation. Keep it under your own control.
A verification code can authorize a particular action. Do not share it with someone claiming to provide support. First ask whether you initiated the action described.
Losing control of a phone or email also affects recovery. Consider the device lock, saved sessions and email security together. Changing one account password does not resolve every kind of compromise.
These points separate the practical questions raised by this subject. Read each one in the context of the conditions described above.
Compare its time and device with your own activity; follow the relevant security process if they do not match.
End contact when someone demands codes using urgency or a prize as a reason.
Avoid accepting help that requires an unknown APK or remote-control app.

Compare its claim with your own activity before following a link. If secrets were shared, act through a familiar security process. Do not provide more information in reply to the suspicious message.
Record the time, message and actions taken. This helps distinguish repeated requests. Remove identity details and codes before showing the record to anyone else.
Stop supplying information to an unexpected request.
Check your phone, email and password security.
Where available, follow instructions to end unfamiliar sessions.
Retain a summary without secrets.
No. Keep secret codes for your own actions private.
Avoid it. One disclosure can expose other accounts.
Follow the relevant processes for protecting the device and contact channels first.
Send only the relevant section with names, phones, codes and sensitive details removed.