skip to content

LOLBAS

Microsoft-signed Windows binaries, scripts and libraries with unintended uses, filed as Execute, Download, AWL bypass or Dump. Interviewers ask what an allowed binary can do and how to detect it.

on this pageshow

questions

6

In the LOLBAS project, what is the catalogue, and what criteria must a file meet to be listed in it?

level: juniorimportance: must knowfreq 38%

answer

  1. community list, not a CVE feed
  2. who signed the file
  3. intended use is not interesting
  4. one stated exception to that rule
  5. four types on the index

basics

~20 s

LOLBAS is a community catalogue of Microsoft-signed Windows binaries, scripts and libraries that have extra, unexpected functionality useful to an attacker. It is a map of what allowed files can do, not a list of vulnerabilities.

solid answer

~40 s

LOLBAS (Living Off The Land Binaries, Scripts and Libraries) is a community-maintained, open-source catalogue. Its README sets three criteria: the file must be **Microsoft-signed**, either native to the OS or downloaded from Microsoft; it must have extra **unexpected functionality**, because documenting intended use is not interesting (application allow-list bypasses are the stated exception); and that functionality must be useful to an APT or red team. A listing is a statement that a legitimate file can do more than its name suggests, so a defender treats it as a hazard label: decide whether the file is needed, who runs it, and what to watch. It is not a patch list, because the files work as designed, and it does not claim to be complete.

go deeper

for a junior

Recall the three criteria: Microsoft-signed, unexpected functionality, useful to an attacker. Say plainly that a listing is not a vulnerability and not proof of compromise.

for a middle

Explain how the index is organised into four types and why the OtherMSBinaries type depends on installed products. Be ready to say what a defender does with a listing instead of patching.

for a senior

Show that you use the catalogue as an input to inventory, review and detection work, and that you can explain its limits: community-maintained, criteria-bound, never a verdict.

for a principal

Frame the catalogue as one input among several to a control decision. Explain why neither membership nor absence should ever be the deciding evidence in a policy.

## What the catalogue is LOLBAS stands for Living Off The Land Binaries, Scripts and Libraries. It is an open-source, community-driven resource: the YAML files in the project's `yml/` folder are the source, and the public site and its API are generated from them. The project's own notice says its content is for educational and informational purposes and that the project does not claim its detection references give complete coverage. For a defender the point is simple. Windows ships, and Microsoft software installs, many legitimate signed files, and some of them can do things their everyday use does not suggest. The catalogue records those things in one place so that an application-control owner, an endpoint engineer or a detection engineer does not have to rediscover them. ## The inclusion criteria The README lists three conditions, and a file must meet all of them: 1. **Be a Microsoft-signed file**, either native to the operating system or downloaded from Microsoft. 2. **Have extra, unexpected functionality.** Intended use cases are not interesting, with one exception: application whitelisting (allow-list) bypasses are included. 3. **Have functionality that would be useful to an APT or red team.** The README then lists what interesting functionality can mean: running code (including pass-through execution of other programs or scripts), compiling code, file operations such as download, upload and copy, persistence, a UAC bypass, credential theft, dumping process memory, surveillance, log tampering, and DLL side-loading without relocating the file. Those are descriptions of function classes, which is the level a defender reads them at. ## What it is not - **Not a vulnerability list.** The files are doing what they were built to do; there is no CVE and no patch to apply. The risk statement is about reach, not a defect. - **Not a malware list.** Listed files are legitimate, signed and often needed. Presence on a host proves nothing about compromise. - **Not complete.** It is a community list, and the repository keeps a backlog file of candidates not yet filed. - **Not Unix and not drivers.** The site's index points Unix binaries to the GTFOBins catalogue and drivers to a separate drivers catalogue. ## How the index is organised As read on 2026-10-04 the index shows 245 rows in four types, matching the repository folders. A fifth folder of three honorable-mention files is not on the index. | Index type | Repository folder | Rows on the index | |---|---|---| | Binaries | `OSBinaries` | 136 | | Libraries | `OSLibraries` | 17 | | Scripts | `OSScripts` | 10 | | OtherMSBinaries | `OtherMSBinaries` | 82 | The fourth type matters operationally: those are Microsoft-signed files that arrive with other Microsoft products (the criteria allow files downloaded from Microsoft), so they exist only on hosts that have the product installed. ## How a defender uses a listing - **As an inventory prompt:** which of these files exist on our hosts, and under which paths? - **As a review prompt:** who runs each one, and is that use needed? - **As a detection prompt:** the entry's detection references and ATT&CK ID are starting points for a rule, not finished rules. - **Not as a verdict:** neither presence nor absence in the catalogue says a file is bad or safe. ## Reading a listing in practice When an entry matters to you, read it in this order: 1. Confirm that the file on your host is the one the entry describes: name, signature and one of the listed paths. 2. Read the categories on its commands to see which kinds of function it has. 3. Read the privileges to see whether a standard account is enough. 4. Check whether your hosts need the file and who runs it. 5. Decide block, constrain or monitor, and record the date of the catalogue you used. ## Terminology and maintenance - A **LOLBin** is a binary, a **LOLScript** a script and a **LOLLib** a library; the project name covers all three. - "Living off the land" means using what the environment already contains instead of bringing new tools. Why an operator chooses that is a different question and belongs to the malware-execution material. - Contributors submit a YAML source file by pull request. CONTRIBUTING.md asks that none of the fields be added or removed, and that categories come from the category list because the website depends on exact labels. - The Unix counterpart is the GTFOBins catalogue, which files its entries by function and context instead of by category.

  • A scanner or report names a binary that is listed in LOLBAS. Do you raise it as a vulnerability to patch?
    No. The file works as designed, so there is no CVE and no fix to apply. Treat the listing as a risk statement: confirm whether the file is needed on that host, who runs it, and whether process-execution monitoring covers it. The decision is to block, constrain or monitor, not to patch.
  • Why does the catalogue have an OtherMSBinaries type, and what does it change for an inventory search?
    The criteria accept Microsoft-signed files downloaded from Microsoft as well as native ones. Those files ship with products such as development tools or Office and live under product folders, so a host that lacks the product lacks the file. An inventory should check the installed products, not assume a base-image path.
  • Why is a binary's absence from the catalogue not a clean bill of health?
    The catalogue is community-maintained and limited by its own criteria: only Microsoft-signed files qualify, and the maintainers decide what is interesting enough. A file can be missing because it was never reviewed, was excluded by policy, or is signed by someone else.

A catalogue entry works like a hazard label on a lab chemical: it says what the substance can do if mishandled so the lab can decide where to store and who may use it. The label is not an accusation against the bottle and not a recipe.

  • LOLBAS is a list of Windows vulnerabilities that need patching
  • Every listed binary is malware and should be removed from the estate
  • A binary that is not listed is safe to allow
  • The catalogue covers any signed file, including third-party tools
  • Microsoft curates and endorses the entries
  • The criteria are about documenting each tool's intended administrative use
open as a page

In a LOLBAS YAML entry, which fields tell a defender where the file lives, what privilege a command needs and how to detect it?

level: middleimportance: should knowfreq 14%

basics

~10 s

Full_Path lists where the file commonly sits. Each command row carries Category, Privileges, MitreID and OperatingSystem. The Detection block holds IOC, Sigma, Elastic, Splunk, BlockRule and Analysis references.

open as a page

What are the fifteen LOLBAS command categories, and which ones matter most when reviewing a Windows application allow-list?

level: middleimportance: should knowfreq 24%

basics

~20 s

LOLBAS files each command under one of fifteen categories: ADS, AWL bypass, Compile, Conceal, Copy, Credentials, Decode, Download, Dump, Encode, Execute, Reconnaissance, Tamper, UAC bypass and Upload. An allow-list owner typically reads Execute, AWL bypass, Download, Dump, Credentials and ADS first.

open as a page

Because the LOLBAS catalogue does not list a signed vendor utility, a change request calls it safe to allow; what is wrong with that reasoning?

level: seniorimportance: should knowfreq 26%

basics

~20 s

Absence from LOLBAS proves nothing. The catalogue is community-maintained and incomplete, covers only Microsoft-signed files by its criteria, and excludes some behaviour on purpose. A vendor-signed tool is outside it by definition, so review the tool's own functions.

open as a page

Using the LOLBAS catalogue, how would you decide what to block, constrain or monitor when trimming Microsoft-signed tools on 800 Windows admin workstations?

level: seniorimportance: should knowfreq 32%

basics

~20 s

Join the catalogue to your inventory and execution logs, then decide per file: block what nobody needs, constrain what one group needs, monitor what is used broadly. Weigh category, privileges and need, and test in audit mode first.

open as a page

What does a LOLBAS entry's Detection block give a detection engineer, and where does it stop being reliable?

level: seniorimportance: nice to knowfreq 14%

basics

~20 s

The Detection block lists IOC items and links to Sigma, Elastic and Splunk rules, BlockRule policies and Analysis write-ups. It is a set of starting points: the project does not guarantee that any of it detects the behaviour.

open as a page