Skip to content

AppLocker Bypass

github-actions[bot] edited this page Nov 19, 2026 · 2 revisions

Known AppLocker bypass techniques (LOLBins and binary abuse) useful during Windows application whitelisting assessments. Source: Pentest Laboratories.

Purpose: Tests whether a Windows AppLocker application-whitelisting policy is actually enforcing what it claims to. AppLocker is frequently deployed with default or overly permissive rules (e.g., allowing anything in C:\Windows or signed-by-Microsoft), and every item on this list is a specific technique for executing arbitrary code despite those rules being "on."

Function: Each entry abuses a signed, whitelisted Windows binary to proxy execution of unsigned attacker code - InstallUtil, Regsvr32, MSBuild, Rundll32, and the rest are all legitimate Microsoft tools that AppLocker's default rules trust by path or publisher, and each has a documented way to make it run arbitrary script or DLL content instead of its intended payload. This is the Windows-specific subset of the broader LOLBins/LOLBAS technique class.

Goal: Establish whether the deployed AppLocker rule set (path-based, publisher-based, or hash-based) actually stops code execution, or whether it just blocks the naive case of double-clicking an unsigned .exe. A thorough pass through this list often reveals that "AppLocker is enabled" and "AppLocker is effective" are two very different claims.

When & How to use this: Run this once you have code-execution-but-restricted access on a system with AppLocker (or WDAC) enforced - either during an authorized red team engagement or a defensive control validation exercise. Test the rule set's actual configuration first (Get-AppLockerPolicy -Effective) to know which rule types apply, since some bypasses only work against path-based rules and are moot against strict publisher/hash rules.

๐Ÿ“– Full deep-dive on the LOLBins used here: Tradecraft/lolbins-lolbas.md



๐Ÿ“– Use These Checklists Responsibly: Authorization is MANDATORY

Attack techniques are powerful - use them ethically and legally.

Repository: ULTIMATE CYBERSECURITY MASTER GUIDE

Maintained by: Pacific Northwest Computers


โš ๏ธ Authorized testing only: confirm authority and scope before active testing. โš ๏ธ

โš ๏ธ Legal consequences depend on the conduct and applicable law; see 18 U.S.C. ยง1030 and DOJ CFAA charging policy. โš ๏ธ

โš ๏ธ For systems you do not own or administer, confirm authorization in advance and document scope in writing where policy, law, or contract requires it. โš ๏ธ

โญ Star this repo if you find it useful! โญ

## Related Files - [README.md](https://github.com/Pnwcomputers/ULTIMATE-CYBERSECURITY-MASTER-GUIDE/wiki/Checklists) - Checklists section index

๐Ÿ“„ Source: Checklists/AppLocker.md | โœ๏ธ Suggest an edit | โฌ…๏ธ Back to Checklists

Clone this wiki locally