Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A fileless attack runs in memory and through built-in system tools, leaving no executable on disk for signature-based scanning to find and little for a forensic image to recover.

What Is a Fileless Attack?
A fileless attack is one that avoids writing a malicious executable to disk. The code runs in memory, is delivered through a script or an exploit, and uses software already present on the system to do its work. Antivirus products that scan files find nothing, because there is no file to find.
The term is slightly misleading, as critics point out: something usually touches disk at some stage, whether a document, a script, a registry value, or a scheduled task definition. “Low-footprint” would be more accurate. The useful distinction is that no portable executable belonging to the attacker ever sits on the file system, which defeats a whole category of detection.
certutil, mshta, rundll32, regsvr32, and msbuild are all signed, present by default, and capable of downloading and executing code. See living off the land.Operation Cobalt Kitty, documented by Cybereason in 2017, is a frequently cited example: an espionage campaign against an Asian corporation that ran for months almost entirely through PowerShell and in-memory payloads. Most ransomware operations now use similar tradecraft up to the point of encryption.
Signature-based scanning depends on a file and a hash. Allow-listing by publisher passes, because the running executable is a genuine Microsoft binary. Disk forensics after the fact recovers very little, and a reboot destroys most of what remained — which is why volatile memory capture has to come before anything else in the response process.
wmiprvse.exe spawning a script host, is anomalous regardless of what the script contains.If you suspect a fileless intrusion, capture memory before isolating or rebooting the host. Network isolation that keeps the machine powered is preferable to pulling the plug. Expect disk artefacts to be sparse and plan to rely on centralised logs, which is only possible if forwarding was configured before the incident rather than during it.
At Privia Security, our digital forensics and incident response services include memory analysis, which is frequently the only place the evidence exists.
Not entirely, in most cases. A delivery document, a script, a registry value, or a scheduled task definition usually touches disk somewhere. What is absent is a malicious executable belonging to the attacker, which is the thing file scanning and hash-based blocking are designed to catch. Low-footprint is a more accurate description than fileless.
Traditional signature scanning cannot, because there is no file to scan. Modern endpoint products detect them through behavioural analysis, command line inspection, AMSI content scanning, memory scanning, and process relationship monitoring. The capability depends on the product being configured to collect that telemetry and on the relevant logging being enabled in Windows.
PowerShell script block logging, through Group Policy, with the events forwarded off the host. It records the deobfuscated content of executed script blocks independently of any security product and catches a large share of fileless activity. Add module logging, process creation auditing with command lines, and Sysmon for module loads and WMI subscriptions.
Capture volatile memory before isolating or rebooting, because the evidence exists only there and a restart destroys it. Prefer network isolation that keeps the host running. Expect disk forensics to yield little, and rely on centrally collected logs, which means the forwarding must already be in place. Plan and rehearse memory capture in advance.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.