Received a message about a stuck parcel, a toll road debt or a tax refund awaiting approval? Do not check it through the link inside it. Open the organisation's familiar app yourself, or go to its website by a route you already know, and check there. This is the key step even when the Hebrew is good, the amount is small and the name looks familiar. If you have already clicked, stop and think about what happened next: opening a page, giving a password and installing software are different situations, and each needs its own response.
Check what the message asks for before checking how it looks
Phishing is an attempt to get you to hand over information or take an action through impersonation. The Bank of Israel describes how a message leads to a page that looks like the website of a familiar organisation and asks for identification or payment details. The design is meant to feel familiar. The useful question is what you are being asked to do, and why it has to be through this particular message.
A demand to enter a password, give a code you have just received, install an app or pay urgently should interrupt the flow. This does not mean every payment request is a scam. It means the request needs to be verified outside the route the sender prepared for you. You can check a real debt without relying on a link that arrived out of the blue.
According to the UK's National Cyber Security Centre (NCSC), scam messages are not always full of mistakes. They can be convincing even to experienced people. So a spelling mistake is a warning sign, but correct Hebrew is no confirmation. Being addressed by your first name is not enough either. You do not need to prove how the sender got your name to choose an independent way of checking.
Notice the pressure the message creates. A threatened fine, a promised refund or a demand to act before the account is closed make it hard to stop. Separate the claimed urgency from your own action: first verify with the organisation, and only then decide whether there is anything to do at all.
Five everyday examples, and the same way to check them
The following examples illustrate possible situations; they are not reports of a specific campaign running right now. A delivery message may ask you to correct an address or make a small payment. If you really did order something, check the order in the app or account you bought it through. Simply waiting for a parcel does not connect your parcel to the message you received.
A message impersonating Israel Post can exploit the same expectation. Use a tracking number you already have from the order, not just the number in the new message. If you do not know who is delivering the parcel, start with the business you ordered from. You do not need to pay to find out whether there is a delivery.
For a message about a blocked bank account, open your bank's app yourself, or call the familiar number on your card or in an official document. Do not call a number the message offers for verification. In the same way, a payment demand from a toll road is checked with the relevant operator through a familiar account, not by the logo in the image.
A tax refund is another example of a promise that tempts you to act quickly. Check the information through the Israel Tax Authority's official channel, or with the professional who handles the matter for you. Do not send a photo of an ID document or card details to open a refund you have not looked into. In every example, changing your point of entry is what gives you back control of the check.
Look at the link address without turning the check into a visit
On a computer, the Bank of Israel recommends checking the destination address by hovering the pointer over the link. In some email programs and browsers, the address is shown without opening the page. Check the actual address, not just the blue text or the label on the button. Text that looks like a website name can point somewhere else.
On a phone, a long press may show options or a preview, depending on the app and settings. Do not assume every preview is disconnected from the internet. If you are not sure how your device behaves, skip checking the link and go straight to the familiar service. You do not need to open a suspicious address to decide not to use it.
As a purely technical example, in the address bank.example.com the word bank is part of the name under the domain example.com. It does not make it a bank's website. An organisation's name appearing before the domain or later in the path does not prove ownership. Long addresses, shortened links and similar names can make reading harder. If deciding requires you to guess, do not decide by the address alone.
HTTPS is not a certificate of honesty for a website either. It concerns protecting the connection, not the trustworthiness of whoever runs the page. Keep to the practical rule: when unsure, open the app you already have installed or use a familiar address you saved earlier. A sponsored search result is no substitute for identifying the right organisation either.
Already clicked? The next step depends on what was given
If you opened a page and entered no information, close it and do not approve any download, notification permission or installation it offers. The click itself does not prove the device has been hacked, but it is also not a check that guarantees nothing happened. Notice whether a file was downloaded or a permission request appeared. On a computer you can run a scan with a trusted security tool and update the browser and operating system, following the support instructions.
If you typed a password, change it through the real website or app, on a device you trust. Also change identical passwords on other services. The NCSC recommends acting on accounts where you used the same password, rather than settling for deleting the message. Do not go back to the suspicious page to correct what you typed.
If you gave a verification code or approved a sign-in request, treat it as a possibility that access to the account was granted. Check activity and active sessions and turn to the service's security or recovery process. Google, for example, advises checking security events, unfamiliar devices and recovery details. Changing the password is an important step, but you also need to check what has changed in the account.
If card details, bank details or a payment approval were given, contact the bank or card company immediately through an independent channel. Describe what you gave and what you approved, and ask for instructions on limiting the damage and checking transactions. Do not wait to see a charge before reporting, and do not assume in advance that the money is lost or that it will be refunded automatically.
A file or app that was installed needs further checking
If a file was only downloaded, do not open it to find out what it is. If you opened or installed something, say so when you ask for help. It is important to distinguish between a downloaded file, an installed app and a granted permission. Note the time, the name of the file or app and what you were asked to approve. These details are more useful than a general description that the phone is behaving strangely.
On a work device, tell the IT or security team and follow their instructions. On a personal device, use familiar support and trusted security tools. Do not install a repair program that came in the same message or from someone who called because of it. If you suspect remote control, stop carrying out sensitive actions on the device and seek help from another device.
Keep a screenshot of the message, the destination address if it is available without opening it, and details of any transaction or charge. Do not spread a screenshot in a group if it contains an active code, a card number or an ID document. A useful report does not require exposing those details to more people. Do not rush to reset the device before you have received instructions, especially if this may erase information needed for the investigation.
In Israel you can report phishing and impersonation to the 119 hotline of the National Cyber Directorate and receive an initial professional response. Such a report does not replace contacting your bank in a financial case or reporting to the police when needed. First deal with the access and the money at risk, then complete the documentation and reporting.
Turn the check into a habit you can remember
There is no need to investigate every message. You can set a simple household rule: a request for money, a password or a code is checked through a separate channel. If you are helping someone else, ask them to stop and describe what the message demands, without clicking to show you. The question of whether an action has already been taken matters more than the question of why they believed it.
Make sure in advance that you have access to the apps and service numbers you use. Turn on security options in your accounts and update your recovery details. When a surprising request arrives, you will have a familiar route for checking. You can also use the guide to checking the source of images when part of the persuasion is based on a photo or an advert, but a matching image does not verify the whole message.
If it turns out you made a mistake, do not dwell on the embarrassment. Prepare a short, accurate description of what was given and act in order of risk. A matter-of-fact response lets the organisation handling the case understand the situation and guide you, even when it is not yet clear whether any damage was done.
Verify a request through an independent channel, and if you have already acted, respond according to the information or permission you actually gave.
Sources and useful links
Links and documentation were checked before publication. Interfaces and features may change. The article images are illustrations, not screenshots of the services.



