mandiant / mandiant/capa-rules
Create new rule with LoadLibrary, etc. APIs
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 736
- Forks
- 245
- Avg merge
- 4d 53m
- Merged PRs (30d)
- 2
Description
I'd say it's fine to remove the optional block, how about we create a new rule with the LoadLibrary APIs (not sure if that's just noisy or helpful).
Originally posted by @mr-tz in https://github.com/mandiant/capa-rules/pull/908#discussion_r1629084813
removed rule features:
- optional:
- characteristic: indirect call
- api: kernel32.LoadLibrary
- api: kernel32.GetModuleHandle
- api: kernel32.GetModuleHandleEx
- api: ntdll.LdrLoadDll
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the removed YAML feature list in this issue and the discussion from PR #908. Search the repository for existing rules using LoadLibrary, GetModuleHandle, GetModuleHandleEx, or LdrLoadDll, then define the new rule around the agreed API set; done means the rule is added and validated consistently with neighboring rules.
Written by the indexing model from the issue text.
Assessment
- Domain
- reverse-engineering, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100