Security & Privacy/Guide/Explainer

What Is a Living-Off-the-Land (LOTL) Attack? A Complete Guide

Nation-state hackers like Volt Typhoon hide for years by using tools already on your network — no custom malware required.

The official seal of the U.S. Cybersecurity and Infrastructure Security Agency, which co-authored the joint advisory on living-off-the-land techniques
CISA co-authored the joint guidance on detecting living-off-the-land techniques with the NSA and FBI. Image: CISA.

Quick facts: living off the land at a glance

  • Living off the land (LOTL) means attackers use tools already built into the operating system — not custom malware — to carry out an intrusion.
  • CISA, the NSA and the FBI, with eight other U.S. and allied agencies, published joint guidance on detecting LOTL activity after the Chinese state-sponsored group Volt Typhoon used it against U.S. critical infrastructure.
  • The advisory says Volt Typhoon maintained access inside some victim networks for at least five years using this technique.
  • MITRE ATT&CK catalogs the core tactic as T1218, "System Binary Proxy Execution," with 14 named sub-techniques covering specific abused binaries.

What is a living-off-the-land (LOTL) attack?

A living-off-the-land attack is an intrusion technique where attackers rely on legitimate software already present on a target system — command-line utilities, scripting engines, administrative tools, and other trusted, often digitally signed binaries that ship with the operating system — instead of installing custom malware. The term, and the shorthand "LOLBins" for the binaries themselves, is credited to security researcher Matt Graeber, and it has since become standard vocabulary across incident-response reports, government advisories and threat-intelligence write-ups alike. The idea is simple: if a tool is already there, already trusted, and already used by legitimate administrators every day, using it for an attack blends malicious activity into the normal background noise of the network.

That's precisely what makes LOTL dangerous. Traditional malware can often be caught by antivirus software matching known file signatures, or by security tools flagging an unfamiliar executable appearing on disk. An attacker running rundll32.exe or PowerShell — programs that are supposed to be there, used constantly by IT staff for routine work — doesn't trip those same alarms. A security analyst looking at a process list sees a Microsoft-signed binary that belongs on every Windows machine in the building; nothing about the process name, its certificate, or its presence on disk looks wrong. The only thing that would look wrong is what it's being told to do and by whom — information signature-based tools were never designed to evaluate.

How LOTL actually works

According to MITRE ATT&CK's entry for System Binary Proxy Execution (T1218), adversaries "bypass process- and signature-based defenses by proxying execution of malicious content with signed, or otherwise trusted, binaries." In practice, that means an attacker doesn't run their malicious code directly — they hand it to a trusted program to run on their behalf. MITRE's page documents 14 named sub-techniques, including:

  • Regsvr32 (T1218.010) and Rundll32 (T1218.011) — Windows utilities meant to register or run code from DLL files, which attackers redirect toward malicious DLLs, sometimes fetched over the network.
  • Mshta (T1218.005) — the Windows utility for running HTML Application files, abused to execute attacker-supplied script.
  • Msiexec, InstallUtil, CMSTP, Odbcconf, Mavinject, MMC and several others — each a legitimate Windows component with a side effect attackers can repurpose to execute arbitrary code.

MITRE notes that on Windows, several of these binaries are Microsoft-signed, so they pass right through systems that enforce digital-signature validation — the very check meant to stop unauthorized code from running. On Linux, the same idea applies to built-in utilities; MITRE specifically cites split as one example of a trusted binary that can proxy malicious commands. The pattern generalizes beyond MITRE's named list to PowerShell, Windows Management Instrumentation (WMI), scheduled tasks, and legitimate remote-administration tools like PsExec — anything already on the machine that can execute commands or move files.

PowerShell in particular is a recurring LOTL workhorse because it's installed by default on every modern Windows machine, has deep access to the operating system, and can download and execute code entirely in memory without ever writing a suspicious file to disk — a technique sometimes called "fileless" attack activity. WMI serves a similar role for lateral movement, letting an attacker run commands on remote machines across a network using infrastructure that's already there for legitimate systems administration. None of this requires the attacker to introduce a single new binary onto the system; every tool involved was installed by Microsoft or the organization's own IT team.

Who uses LOTL, and why

LOTL techniques show up most prominently in nation-state espionage, where staying undetected for months or years matters more than moving fast. The clearest public example is Volt Typhoon, a People's Republic of China state-sponsored group that CISA, the NSA and FBI say pre-positioned itself inside U.S. critical-infrastructure networks — communications, energy, transportation and water utilities — relying heavily on native tools specifically to blend into normal administrator activity. The joint advisory, AA24-038A, states the group "has maintained access in some victim environments for at least five years," using that time to study network architecture in case it needed to disrupt operational technology during a future crisis.

MITRE's T1218 page also names Lazarus Group, the North Korea-linked threat actor, which used wuauclt.exe — the Windows Update Client — to execute a malicious DLL as part of a persistence mechanism delivered through LNK shortcut files. Ransomware operators and financially motivated criminal groups use the same general approach for a more mundane reason: it lets them move laterally through a victim's network using tools the victim's own IT team already relies on, without needing to smuggle in a custom toolkit that endpoint security might catch.

Not every state-linked intrusion uses pure LOTL tradecraft — some combine it with custom-built tools. A recent China-linked espionage campaign against VMware vCenter relied on a bespoke post-exploitation tool to create a rogue admin account rather than native utilities alone, which shows the two approaches — custom malware and living off the land — often sit side by side in a single intrusion rather than being an either-or choice. Volt Typhoon itself fits the broader pattern security researchers classify as an advanced persistent threat (APT): a well-resourced, patient actor focused on long-term access rather than a quick smash-and-grab, for whom avoiding detection for months or years is the entire point, making LOTL tradecraft a natural fit.

Ransomware affiliates borrow the same playbook for a more immediate reason: speed and reliability. Using tools a victim's own IT staff already trust to run means an intrusion is less likely to be interrupted mid-attack by an endpoint security product flagging an unfamiliar file, which matters when the goal is to reach and encrypt as many systems as possible before anyone notices. Security researchers have also documented LOTL activity used purely for reconnaissance — mapping out a network with native tools like net.exe, nltest.exe or PowerShell's own Active Directory cmdlets — well before any destructive payload is deployed.

LOTL vs. traditional malware

The two approaches aren't mutually exclusive, and plenty of intrusions use both at different stages — a custom tool to gain initial access, then native utilities to move laterally and stay hidden once inside. But the detection challenge each one poses is genuinely different, which is why security teams can't rely on a single tool or technique to catch both:

CharacteristicTraditional malwareLiving off the land
What runs on the systemA new, attacker-supplied executable or scriptTools already installed by the operating system or IT admins
Signature-based antivirusCan often detect known malware signaturesLargely ineffective — the binary itself is legitimate and signed
Primary detection methodFile scanning, hash matchingBehavioral analysis and logging of command-line activity
Typical usersBroad range, including opportunistic criminalsNation-state APT groups, ransomware crews seeking stealth
Forensic footprintNew files, unfamiliar processesNormal-looking admin activity, harder to distinguish from legitimate use

How defenders detect and mitigate LOTL activity

Because the tools themselves are legitimate, defending against LOTL activity is fundamentally a detection problem, not a file-scanning one. The CISA-led joint guidance on identifying and mitigating LOTL techniques, co-authored with the NSA, FBI, the Departments of Energy and Transportation Security Administration, and cyber agencies from Australia, Canada, the UK and New Zealand, exists specifically because, as the agencies put it, many organizations "do not implement security best practice capabilities that support detection of LOTL," which is exactly why the technique keeps working with so little investment in tooling from the attacker's side.

The companion advisory on Volt Typhoon lists concrete actions organizations can take immediately: patch internet-facing systems, prioritizing the specific appliance vulnerabilities the group is known to exploit; turn on comprehensive application, access and security logging and send those logs to a central system attackers can't easily tamper with; implement phishing-resistant multi-factor authentication; and plan for retiring any technology that has aged out of its manufacturer's support lifecycle. Further recommended measures include limiting how exposed management interfaces are to the internet, never storing credentials on edge devices, restricting RDP usage, enforcing least-privilege on administrator accounts, and segmenting operational technology networks from general IT networks so that a LOTL foothold in one doesn't automatically grant reach into the other.

The common thread across all of it is baselining: knowing what normal administrative tool usage looks like on a given network well enough that a PowerShell session or a rundll32 invocation outside that baseline stands out, rather than disappearing into routine noise.

Why zero trust principles help against LOTL

Several of the joint guidance's recommendations — least-privilege administrator accounts, network segmentation, and not trusting a device just because it's already inside the perimeter — are also the core tenets of a zero trust security architecture. That overlap isn't a coincidence: LOTL attacks specifically exploit the assumption that activity from a trusted internal tool, running under a legitimate account, on a device already inside the network, must be legitimate. Zero trust's continuous verification model removes exactly that assumption, requiring every action to be checked against policy regardless of where it originates or what tool is doing the asking, which closes much of the gap that makes LOTL effective in the first place.

What to do next

If you manage IT infrastructure, the single highest-leverage step is turning on centralized logging for command-line and script-execution activity — most LOTL detection failures trace back to logs that simply weren't being collected, not to a tool that couldn't have caught the behavior. If you're a security leader evaluating your organization's exposure, read the CISA-led joint guidance directly rather than relying on summaries, since the specific detection recommendations for your environment's native tools matter more than the general concept. And if you're trying to understand a specific incident, check whether the attacker used named LOLBins like regsvr32, rundll32 or mshta, since MITRE's sub-technique pages for each one list the exact command-line patterns and log sources defenders should be watching.

None of this requires exotic new tooling to start. Most organizations already own the logging infrastructure needed to begin baselining normal PowerShell, WMI and admin-tool usage; the gap is usually that logging isn't turned on broadly enough, or nobody is reviewing it for the kind of statistically unusual activity LOTL produces once you know what to look for.

Frequently asked questions

What does "living off the land" mean in cybersecurity?

It means an attacker uses tools already built into the operating system — like PowerShell, rundll32 or WMI — instead of custom malware, so their activity blends into normal administrator behavior and is harder to detect.

Why can't antivirus software catch LOTL attacks?

Traditional antivirus mainly matches known malware signatures or flags unfamiliar executables. LOTL attacks use legitimate, often Microsoft-signed binaries that are supposed to be on the system, so there's no new file or signature to catch.

Who is Volt Typhoon?

Volt Typhoon is a China state-sponsored hacking group that CISA, the NSA and the FBI say pre-positioned itself inside U.S. critical-infrastructure networks using living-off-the-land techniques, maintaining access in some victim environments for at least five years.

What is a LOLBin?

A LOLBin ("living-off-the-land binary") is a legitimate, trusted program already on a system that attackers repurpose to run malicious commands, such as regsvr32, rundll32 or mshta on Windows.

How can organizations detect LOTL activity?

Primarily through centralized logging of command-line and script activity, baselining what normal administrative tool usage looks like, enforcing least-privilege accounts, and applying phishing-resistant multi-factor authentication, per CISA's joint guidance with the NSA and FBI.

Is living off the land the same as a zero-day attack?

No. A zero-day exploits an unpatched software flaw, while living off the land is about which tools an attacker uses after gaining access. The two are unrelated and can be combined or used independently.

Sources

More on Living off the Land (LOTL) →Living off the LandLOTLVolt TyphoonCybersecurityMITRE ATT&CK
Sana Qureshi
Written bySana Qureshi

Sana Qureshi runs the security and privacy desk. She reports on actively exploited vulnerabilities, vendor patches and data breaches, and covers the password managers, VPNs and authentication tools readers use to protect themselves. Her alerts cite vendor advisories, CISA and the CVE record directly.

More from Security & Privacy

See all