mandiant/capa-rules

detect uncommon .NET entry points

Open

#725 opened on Mar 16, 2023

View on GitHub
 (1 comment) (3 reactions) (0 assignees) (234 forks)github user discovery
good first issuerule idea

Repository metrics

Stars
 (721 stars)
PR merge metrics
 (PR metrics pending)

Description

This article describes multiple .NET entry points, where some of these are often leveraged by malware and obfuscators. I think it beneficial to bring these uncommon, or commonly malicious, entry points to the attention of capa users to help guide analysis to interesting code.

Contributor guide

Research direction
Read the linked article to understand uncommon .NET entry points, then create capa rules that detect those entry points in .NET binaries.
Tech stack
pythoncsharp
Domain
securityreverse engineering
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
.NETcapa rules
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65