Book an intro call NL

Blog › Skyw4lker: device code phishing targets US businesses

Skyw4lker: device code phishing targets US businesses

Published

Skyw4lker targets US organisations with device code phishing. Learn how the technique works and how to protect your business accounts.

Attackers can gain access to business accounts without asking anyone to enter a password on a fake login page. A short summary of a report from The Hacker News, dated 28 October 2026, describes Skyw4lker. This device code phishing campaign primarily targets US organisations.

This form of phishing abuses an existing process for giving devices or applications access to an account. You can land on a genuine login page and still grant access unintentionally. The available summary is cut off. It provides no further details about the messages used in Skyw4lker or the campaign’s impact.

What is known about Skyw4lker

The Hacker News refers to an analysis of Skyw4lker by ANY.RUN. According to the available summary, the campaign mainly targets organisations in the United States. It uses device code phishing, where an attacker abuses a sign-in process that involves a device code.

The summary describes how modern phishing can use legitimate cloud services and trusted business workflows to access corporate accounts. Traditional credential theft is not always necessary. Obvious warning signs, such as a fake login page, may therefore be absent.

The source does not establish anything more. It gives no figures for affected organisations or financial losses. Nor does it explain which messages the attackers use as bait or which services they abuse.

The following sections therefore explain device code phishing in general. They describe how this type of attack can work, not specific actions confirmed in the Skyw4lker campaign.

How device code phishing works

A genuine feature is used for the wrong purpose

Some applications cannot easily handle a full sign-in process themselves. A device code flow provides a way around this. The application displays a code and directs you to a login page. You open that page on another device and enter the code.

Once you sign in, the original application gains access within the permissions granted. The code links your sign-in to an application waiting elsewhere.

In normal use, you start this process yourself. You know which device or application you want to connect. In device code phishing, an attacker tries to get you to use a code linked to their own sign-in attempt.

The attacker starts the process, the employee confirms it

A possible attack works like this:

  1. The attacker starts a sign-in process for an application or device they control. This generates a device code.
  2. The attacker tries to persuade an employee to enter that code on the relevant login page.
  3. The employee signs in with their business account. Depending on the sign-in process, they may also be asked for an additional confirmation.
  4. Completing the sign-in allows the waiting application to gain access as that employee.

This is a general description. The available summary does not explain how Skyw4lker persuades employees to enter this process.

The deception largely lies in the explanation that accompanies the code. An attacker needs to give you a reason to enter it. If you think you are completing a routine work task, you may approve a sign-in you never requested.

Why a genuine login page is not enough

Many people are taught to check the web address before signing in. That remains useful. But in this attack, the login service’s address may be genuine.

An additional sign-in confirmation does not prove that the request is legitimate either. A valid confirmation can still complete the wrong sign-in attempt. The technology verifies your identity, while you have been misled about the purpose.

So do not just ask whether the web address is correct. Also ask: which application am I giving access to, and did I start this process myself?

An employee does not have to be careless to fall for this. A request that fits their expected work can look credible. That is especially true when the page that follows is the same one they use for everyday sign-ins.

What this means for businesses

For a small or medium-sized business, unauthorised account access can affect more than the employee who enters the code. What an attacker can do depends on the account’s permissions and the access granted to the application.

If that access includes email, an attacker may be able to read business correspondence. They could use it to gather information for a further deceptive request. Messages sent from a familiar account may also seem trustworthy to colleagues or business contacts.

If shared documents are accessible, business information may be exposed too. The consequences depend on what the account can open. These are possible effects of account misuse, not reported outcomes of the Skyw4lker campaign.

Even without confirmed data theft, recovery takes work. An administrator needs to establish what access was granted and what happened in the account. The employee may need to stop using the affected account temporarily.

Existing messages may also come into question. Did the employee send a request, or did someone with unauthorised access send it? Resolving that uncertainty can delay payments or ongoing work.

If your business outsources its IT, you need clear arrangements with your IT provider. Who can revoke access? Where should an employee report entering a device code? Those arrangements need to be available before anyone needs them.

How to recognise device code phishing

Not every request involving a device code is suspicious. But the reason for the request and the application involved should match what you are doing. Watch for these signs:

  • You did not start a connection process. Yet a message asks you to enter a device code or complete a sign-in.
  • The reason is unclear. The request does not clearly explain which application will gain access or why it needs it.
  • The code comes from someone else. You receive it in a message, even though you are not trying to sign in on a device or connect an application.
  • The application does not fit your task. The sign-in screen names an application you do not expect or recognise.
  • The request asks for additional sign-in confirmation without a clear reason. Being able to provide that confirmation does not make the request trustworthy.
  • The sender asks you to ignore security questions. For example, you are told to continue without understanding what access you are granting.

Check unexpected requests even when they come from a familiar account. A trusted sender does not guarantee that the account owner sent the message.

What employees and organisations can do

For employees

  1. Stop if you did not start the process. Do not enter a device code you have been sent just to see what happens next.
  2. Check the request independently of the message. Call the sender on a number you already have. Ask which application needs to be connected.
  3. Read the sign-in screen before confirming. Check whether the named application fits your work. Ask your administrator to explain if you cannot establish this.
  4. Report a suspicious code through the agreed channel. Keep the original message so your administrator can investigate what prompted the request.
  5. Report it immediately if you have already confirmed. Explain that you entered a device code and which steps you completed afterwards. Do not delete the message.

For the organisation

  • Document where device codes are used. Have your administrator establish which business applications need this sign-in method.
  • Restrict the method where technically possible and appropriate. Do not leave unused sign-in options available without a reason.
  • Provide a reporting route outside the business account. Employees must still be able to reach support if access to their account is temporarily blocked.
  • Investigate the access granted when a report comes in. Check which application was involved and what permissions the account has.
  • Revoke unwanted access where it has been granted. Have your administrator review active sessions and granted permissions. Do not assume that changing the password alone ends all access.
  • Practise recognising attacks that use a genuine login page. Teach employees to check why they are being asked to sign in, not just the web address.

How Lumyo Awareness helps

With Lumyo Awareness, we recreate this type of attack in a phishing simulation. Awareness training helps employees understand why a genuine login page can still be part of a phishing attack. They practise checking what prompted a sign-in request and reporting one they did not expect.