Skyw4lker Campaign Uses Device-Code Phishing to Target U.S. Organizations

Summary
ANY.RUN describes Skyw4lker, a device-code phishing campaign targeting U.S. organizations with business-themed documents and Microsoft authentication flows, and outlines sandbox and threat-intelligence workflows for detection.
Key points
- ANY.RUN says Skyw4lker has targeted manufacturing, technology, and healthcare organizations.
- The campaign uses password-protected business-themed documents to direct victims through sites[.]google[.]com to a Microsoft authentication flow.
- The attacker initiates a device authorization request and can obtain Microsoft 365 tokens if a victim completes it.
- ANY.RUN identified obfuscated JavaScript and a PHP backend used to create victim sessions, collect IP and geolocation data, and poll for authentication completion.
- The article recommends analyzing the document, browser activity, redirects, authentication, and network communication together; static inspection alone may miss the behavior.
- ANY.RUN says its internal analysis found up to 30% of unique malicious IOCs in sandbox sessions were already present in its Threat Intelligence Feeds.
Article Details
- Defense Focus
- Detect device-code phishing by correlating the initial document lure with browser activity, authentication events, and the supporting web infrastructure.
- Detection Methods
- Safely execute and interact with suspicious documents and URLs in an isolated sandbox to observe behavior that static inspection may miss.
- Trace redirects, browser activity, authentication flows, and network communication to connect the lure with the subsequent account-compromise activity.
- Search suspicious indicators against threat intelligence and historical or cross-customer telemetry to identify related activity.
- Use behavioral evidence from sandbox investigations to validate alerts and build detections for observed activity.
- Data Sources
- Suspicious documents and URLs
- Browser activity, redirects, and JavaScript execution
- Authentication events and Microsoft 365 token activity
- Network communication with the campaign backend
- IP address and geolocation information collected during victim sessions
- Threat intelligence feeds and historical customer telemetry
- Rule Types
- IOC-based matching and monitoring
- Platforms
- SIEM
- TIP
- XDR
- Defensive Actions
- Investigate suspicious documents and URLs in an isolated sandbox rather than relying only on static inspection.
- Correlate document, web, authentication, and infrastructure evidence when reviewing apparently valid authentication events.
- Match validated malicious indicators against current and historical telemetry to identify related activity and potentially affected users.
- Feed investigation-derived intelligence into existing monitoring and detection processes through API/SDK, STIX/TAXII, SIEM, TIP, or XDR integrations.
MITRE ATT&CK
T1059.007 · JavaScriptThe campaign page uses obfuscated JavaScript, whose execution and behavior are examined during sandbox analysis.T1528 · Steal Application Access TokenAfter a victim completes the attacker-initiated device authorization flow, the attacker can obtain access to the resulting Microsoft 365 tokens.T1566.001 · Spearphishing AttachmentSkyw4lker uses a password-protected document presented as a contract or service proposal as the initial phishing lure.
Vendors
Products
Countries
Industries
Healthcareshows how this works in practice. The campaign has focused on manufacturing, technology, and healthcare, using business-themed documents, Google-hosted infrastructure, and Microsoft authentication flows toManufacturingprimarily targeting U.S. organizations, shows how this works in practice. The campaign has focused on manufacturing, technology, and healthcare, using business-themed documents, Google-hosted infrastructure, andTechnologyU.S. organizations, shows how this works in practice. The campaign has focused on manufacturing, technology, and healthcare, using business-themed documents, Google-hosted infrastructure, and Microsoft
