Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is AMSI Bypass?

An AMSI bypass disables or blinds the Windows Antimalware Scan Interface so that scripts and in-memory payloads reach the runtime without being inspected by the installed security product.

Illustration for the cybersecurity term AMSI Bypass
Home / Blog / Cybersecurity Terms / What Is AMSI Bypass?
17 November 2026

What Is AMSI Bypass?

What Is AMSI Bypass?

The Antimalware Scan Interface (AMSI) is the hook Microsoft added in Windows 10 so that security products can inspect content after it has been decoded but before it is executed. PowerShell, VBScript, JScript, the .NET runtime, Office VBA, and Windows Script Host all pass buffers to AMSI, which forwards them to whichever antimalware provider is registered. An AMSI bypass is any technique that stops this handover happening, or makes it always return a clean verdict.

It matters because AMSI is the main reason script-based attacks stopped being trivially easy. Encode a PowerShell command in Base64 and AMSI still sees the decoded script at the moment it runs. Attackers therefore spend considerable effort on turning AMSI off, and MITRE ATT&CK catalogues the result under T1562.001, Impair Defenses: Disable or Modify Tools.

How AMSI Works

A scriptable host loads amsi.dll into its own process, calls AmsiInitialize, then passes each buffer to AmsiScanBuffer or AmsiScanString. The provider returns a result, and a value of AMSI_RESULT_DETECTED causes the host to refuse to run the content. The critical design detail is that all of this happens inside the user’s own process, in user mode, with the user’s own privileges. Code already running in that process can modify it.

Common Bypass Techniques

Where It Fits in an Intrusion

AMSI bypasses are rarely the first step. They appear after initial access, when an operator wants to run a credential dumper, a C2 agent, or a reconnaissance script in memory. Offensive frameworks ship them as standard: Cobalt Strike, Covenant, and PowerShell Empire all include AMSI handling, and commodity loaders distributed with infostealers do the same. The technique sits naturally alongside ETW tampering, because together they remove the two main sources of script and runtime telemetry on a Windows host.

Detecting and Containing Bypasses

Treat AMSI as one sensor among several rather than a control you rely on.

Microsoft hardened parts of this in later Windows builds, and AMSI providers can run in a protected process, but the fundamental exposure remains: a user-mode scanning interface sitting inside the process it is meant to police.

We exercise AMSI and endpoint evasion routinely during our Red Team services, because the honest question is not whether a bypass exists but whether your SOC sees the attempt.

FAQ – Frequently Asked Questions

Does an AMSI Bypass Require Administrator Rights?

No. The common techniques patch memory inside the attacker’s own process or set a field in the PowerShell runtime, both of which a standard user can do. That is a direct consequence of AMSI being a user-mode interface loaded into the host process. Administrator rights are needed only for machine-wide changes, such as unregistering a provider under the local machine hive.

If AMSI Is Bypassed, Is My Antivirus Useless?

Not useless, but one of its sensors has been removed. File scanning, kernel callbacks, driver-level telemetry, and behavioural detections still operate, and a modern endpoint detection and response product draws on several sources. The practical effect is that in-memory scripts and reflectively loaded assemblies stop being inspected, which is exactly the content attackers most want to run.

Can Script Block Logging Catch a Bypass?

Often, yes. PowerShell writes event 4104 containing the deobfuscated script block, and it does so independently of AMSI. Many bypass attempts are therefore recorded in full in the Microsoft-Windows-PowerShell/Operational log before the bypass is effective. Collect those events centrally, because an attacker with local administrator rights can clear or stop the local log afterwards.

How Do We Reduce the Opportunity for This?

Remove the PowerShell 2.0 engine, enforce application control so that unsigned scripts run in Constrained Language Mode, restrict who may run scripting hosts at all, and forward script block and process telemetry to a SIEM. None of these stops a determined operator, but together they turn a silent bypass into an event that leaves several correlated traces.

Related Terms

You May Be Interested In These

What Is a Remote Access Trojan?

Cybersecurity Terms

17 November 2026

What Is a Remote Access Trojan?

Read More
What Is TLS (Transport Layer Security)?

Cybersecurity Terms

17 November 2026

What Is TLS (Transport Layer Security)?

Read More
What Is Cloud Backup and Recovery?

Cybersecurity Terms

17 November 2026

What Is Cloud Backup and Recovery?

Read More