Skip to content

Add WWAHost.exe AppX-hosted JavaScript execution entry - #527

Open
Liran017 wants to merge 1 commit into
LOLBAS-Project:masterfrom
Liran017:add-wwahost
Open

Liran017 wants to merge 1 commit into
LOLBAS-Project:masterfrom
Liran017:add-wwahost

Conversation

@Liran017

@Liran017 Liran017 commented Oct 1, 2026 •

Copy link
Copy Markdown
Contributor

This PR adds WWAHost.exe, the Microsoft-signed Windows Web App Host, based on Huntress research published September 29, 2026.

The documented technique registers an AppX package whose ContentUriRules grants WindowsRuntimeAccess="all" to an attacker-controlled origin. The package then loads attacker-hosted JavaScript inside WWAHost.exe with Windows Runtime access. Huntress reports no UAC prompt, SmartScreen prompt, or signature check during the demonstrated flow.

The published proof of concept demonstrated OAuth refresh-token theft through Microsoft’s legitimate login flow, with the stolen tokens surviving MFA. The entry carries two command items for the same registration step: the execution behaviour as Category: Execute / T1218 (System Binary Proxy Execution), and the demonstrated outcome as Category: Credentials / T1528 (Steal Application Access Token).

Registration runs as a standard user, but Developer Mode must already be enabled or an enterprise sideloading policy must permit registration. Without that prerequisite, Add-AppxPackage -Register fails with 0x80073CFF. Huntress tested the technique on Windows 11 24H2, build 26100.

Huntress also provides a Sigma rule detecting the MSAppHost/3.0 user agent communicating with non-Microsoft hosts.

@Liran017
Liran017 marked this pull request as ready for review October 1, 2026 12:13
@Liran017
Liran017 requested a review from a team as a code owner October 1, 2026 12:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant