capa-rules/communication/named-pipe/write/write-pipe.yml
Willi Ballenthin c1d20764ad
use "span of calls" scope (#973)
* use sequence scope instead of thread scope for "static: function" rules

* use sequence scope instead of thread scope for "static: basic block" rules

* make runtime linking rules more concise

* doc: describe sequence scope

* rename "sequence" scope to "span of calls" scope

* Update anti-analysis/anti-av/check-for-sandbox-and-av-modules.yml

Co-authored-by: Mike Hunhoff <mike.hunhoff@gmail.com>

* Update anti-analysis/anti-vm/vm-detection/check-for-windows-sandbox-via-device.yml

Co-authored-by: Mike Hunhoff <mike.hunhoff@gmail.com>

* Update collection/get-geographical-location.yml

Co-authored-by: Mike Hunhoff <mike.hunhoff@gmail.com>

* Update collection/file-managers/gather-classicftp-information.yml

Co-authored-by: Mike Hunhoff <mike.hunhoff@gmail.com>

* Update collection/database/wmi/reference-wmi-statements.yml

Co-authored-by: Mike Hunhoff <mike.hunhoff@gmail.com>

* Update collection/database/sql/reference-sql-statements.yml

Co-authored-by: Mike Hunhoff <mike.hunhoff@gmail.com>

---------

Co-authored-by: Mike Hunhoff <mike.hunhoff@gmail.com>
2025-01-29 10:27:13 +01:00

25 lines
735 B
YAML

rule:
meta:
name: write pipe
namespace: communication/named-pipe/write
authors:
- moritz.raabe@mandiant.com
- michael.hunhoff@mandiant.com
scopes:
static: function
dynamic: span of calls
mbc:
- Communication::Interprocess Communication::Write Pipe [C0003.004]
examples:
- C91887D861D9BD4A5872249B641BC9F9:0x401A77
features:
- or:
- and:
- or:
- match: create pipe
- match: connect pipe
- api: kernel32.WriteFile
- api: kernel32.TransactNamedPipe
description: writes and reads pipe in single operation
- api: kernel32.CallNamedPipe
description: connects, writes, and reads pipe in single operation