Skip to content
skopnix
← Sigma detections

Sigma · CVE exploitation

IIS / ASP.NET stack: IIS worker process wrote a new ASP.NET page

severity
medium
confidence
55/100
generated
14 Nov 2026

w3wp.exe created or renamed an .aspx / .ashx / .asmx / .asp / .config file. Dropping a web shell into the site folder is the usual way to keep access after an IIS-stack RCE. Not specific to one bug: it fires on code execution through the IIS / ASP.NET stack by any route. Attached to the 7 CVEs in this stack that skopnix reported in the last 30 days, newest CVE-2026-118151, CVE-2026-118149, CVE-2026-106931.

False-positive notes

Needs w3wp.exe as the writer and an ASP.NET / ASP page or web.config as the file. The ASP.NET compilation folder (Temporary ASP.NET Files) is excluded. CMSs that write pages on publish will match: baseline per site before alerting.

References

Download .yml
title: 'Skopnix - IIS / ASP.NET stack: IIS worker process wrote a new ASP.NET page'id: 35de1b31-e3de-578b-a261-23311235efd5status: experimentaldescription: 'w3wp.exe created or renamed an .aspx / .ashx / .asmx / .asp / .config file. Dropping a web shell into the site folder is the usual way to keep access after an IIS-stack RCE. Not specific to one bug: it fires on code execution through the IIS / ASP.NET stack by any route. Attached to the 7 CVEs in this stack that skopnix reported in the last 30 days, newest CVE-2026-118151, CVE-2026-118149, CVE-2026-106931.'references:  - https://skopnix.com/cve/CVE-2026-118151  - https://skopnix.com/cve/CVE-2026-118149  - https://skopnix.com/cve/CVE-2026-106931  - https://skopnix.com/cve/CVE-2026-65660  - https://skopnix.com/cve/CVE-2025-53771  - https://skopnix.com/cve/CVE-2025-53770  - https://skopnix.com/cve/CVE-2019-18935author: skopnixdate: '2026-11-14'tags:  - attack.execution  - attack.t1505.003  - cve.2026-118151  - cve.2026-118149  - cve.2026-106931  - cve.2026-65660  - cve.2025-53771  - cve.2025-53770  - cve.2019-18935logsource:  category: file_event  product: windowsdetection:  selection_writer:    Image|endswith: \w3wp.exe  selection_file:    TargetFilename|endswith:      - .aspx      - .ashx      - .asmx      - .asp      - .config  filter_temp:    TargetFilename|contains: Temporary ASP.NET Files  condition: selection_writer and selection_file and not filter_tempfalsepositives:  - Applications that publish pages from inside the site (some CMS editors, upload features) and ASP.NET temporary files outside the excluded folderlevel: medium

skopnix-sigma-cve-stack-iis-dotnet-w3wp-writes-page-811af17a.yml

How to deploy on Sigma

Step 1
Convert for your SIEM with sigma-cli / pySigma, e.g. sigma convert -t splunk -p sysmon rule.yml.
Step 2
Run it as a hunt first: every rule ships as status experimental.
Step 3
Promote to an alert once a week of results is clean on your data.
Check
The processing pipeline must map the logsource (firewall, dns, proxy, webserver, process_creation) to your field names.