Guides

How to Recognize and Handle Phishing and Fake Messages and Requests

Phishing is a fraudulent technique that exploits seemingly trustworthy messages or requests to obtain sensitive information or direct victims to malicious websites. Published cases show that messages may come from a compromised account or exploit an impersonated legitimate domain, so relying solely on the sender’s name or organization is not sufficient.

Phishing is a fraudulent technique in which fake requests from a legitimate email domain have been used to obtain sensitive information. Messages may appear to come from a known company, government agency, or business partner, and may also be sent from a compromised corporate account.

How does phishing work?

Published incidents illustrate several phishing scenarios:

  • An attacker may gain access to an employee’s email account and use it to send messages to colleagues, partners, or people who have previously communicated with the organization.
  • Messages may contain links leading to malicious websites.
  • An attacker may use an address or domain that appears to belong to a legitimate organization to send fake requests for information.
  • Stolen credentials and spoofed addresses impersonating business partners may be used to persuade accounting departments to redirect payments.
  • According to warnings in the sources, artificial intelligence tools may help make phishing messages more convincing and personalize them at scale.

Steps for handling an unexpected message

  • Do not open unexpected links or attachments. The Digital Agency of Japan advised affected individuals not to open links or attachments in unexpected communications.
  • Do not send passwords or card details by email or phone in response to an unexpected request. The agency reminded people that its employees will not request this information in this way.
  • Verify the request through an independent channel. The appearance of a legitimate domain or a known organization’s name alone does not prove that a request is genuine; Revolut confirmed that fake requests were sent from an email domain belonging to a legitimate government agency.
  • Handle requests to change payment details with caution. The business email compromise case shows that impersonating a business partner may be used to redirect transfers to accounts controlled by attackers.
  • Delete the message after receiving guidance from the relevant organization. Nikkei asked recipients to delete messages sent from the compromised account.

What should an organization do?

  • Change passwords associated with a suspected compromised account. Nikkei changed passwords after discovering the incidents.
  • Isolate the affected device or account. The Digital Agency of Japan isolated the affected device from external communications and suspended the account of the maintenance employee involved.
  • Monitor for signs of unauthorized access. The agency began an investigation after detecting broad access to files using a maintenance account, while Nikkei said it had not detected unauthorized logins after changing passwords.
  • Notify affected recipients or customers directly. Nikkei contacted recipients individually, and Revolut said it notified affected customers directly.
  • Notify the appropriate authorities when an incident occurs. Revolut said it notified the relevant government agency, law enforcement, and related financial regulators, while the Digital Agency of Japan reported the incident to the Personal Information Protection Commission.

How can an organization reduce the chances of phishing succeeding?

  • Complete essential security measures and reduce the attack surface.
  • Replace legacy systems that no longer receive security updates.
  • Do not delay installing security updates.
  • Plan on the assumption that an attacker may gain entry to the system, and prepare to respond to warning signs.
  • Make security awareness and culture part of protection, as Dutch authorities linked the importance of basic measures to employee and manager awareness.

Limits on what can be inferred

Published cases do not prove that every message from a legitimate domain is fake, nor do they always specify the amount of data exposed or how long attackers had access. The sources also do not provide a single measure that guarantees phishing can be prevented entirely. The steps above should therefore be treated as precautionary measures based on the reported facts, with the affected organization or internal security team consulted when an incident is suspected.