Potential Persistence Via New AMSI Providers - Registry
Detects when an attacker adds a new AMSI provider via the Windows Registry to bypass AMSI (Antimalware Scan Interface) protections. Attackers may add custom AMSI providers to persist on the system and evade detection…
Description
Detects when an attacker adds a new AMSI provider via the Windows Registry to bypass AMSI (Antimalware Scan Interface) protections. Attackers may add custom AMSI providers to persist on the system and evade detection by security software that relies on AMSI for scanning scripts and other content. This technique is often used in conjunction with fileless malware and script-based attacks to maintain persistence while avoiding detection.
Detection logic
Detection requirements
- Log source product
- windows
- Log source category
- registry_set
Known benign triggers
- Legitimate security products adding their own AMSI providers. Filter these according to your environment.
MITRE ATT&CK mappings
Not mapped to ATT&CK.
References
| Reference | Cited by |
|---|---|
| github.com/gtworek/PSBits/blob/8d767892f3b17eefa4d0668f5d2df78e844f01d8/FakeAMSI/FakeAMSI.c | Only this detection cites it |
| persistence-info.github.io/Data/amsi.html | Only this detection cites it |
From the source
- At source
- Open at source
- Upstream identifier
- 33efc23c-6ea2-4503-8cfe-bdf82ce8f705
- Tagged by the source as
- attack.persistence
Licence
- Published under
- Detection Rule License 1.1Read the licence
- Attribution
- Required
Authorship
- Published
- Aug 26, 2026
- Version
- 1