What to check
An encrypted connection protects data in transit to the named host. Account recovery and payment status each require their own records.
Pick the first action by what happened
Read the original notice and write down what changed. Then choose the account, recovery or payment step that addresses that change.

| What you see | First action | Evidence to keep |
|---|---|---|
| OTP you did not request | Leave any form opened from the message. Check the account through your saved Winbox address. | Time, sender and the purpose shown in the message, with the code hidden |
| Unfamiliar sign-in | Open the known account route, review recent activity and use its recovery steps if needed. | Notice wording, device label and time |
| Payment you do not recognise | Pause new payments. Compare the account history with your bank or wallet record. | Amount, currency, status and transaction reference |
| Password reset you did not start | Check the recovery channel independently. Secure the email or phone account that receives reset messages. | Reset time and any change you did not authorise |
Report the incident with the smallest useful record
Take a payment example. The bank shows RM40 at 9:12 p.m. and Winbox shows a pending request for the same amount. Record both identifiers before drawing a conclusion. If the request belongs to an earlier transaction, say which one and include its time. If you cannot account for the debit, contact Winbox through its published route and follow your payment provider’s reporting process. Leave passwords, payment PINs and OTPs out of the message.
How to use the record
Identify the control your issue involves before taking action. A rejected password needs account recovery, while an unfamiliar payment needs the transaction reference and recorded status. Save the relevant notice without exposing codes or credentials, then open Winbox Contact independently to ask what can be reviewed.
