Add .NET AoT & TouchSocket linking detection #948
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Still Hsu <[email protected]>
|
Oh, wow, sorry this fell of our radar! Great updates here. If you can create a small/faster test binary that would be amazing! |
Still34
added a commit
to Still34/capa-testfiles
that referenced
this pull request
Nov 28, 2024
Signed-off-by: Still Hsu <[email protected]>
Signed-off-by: Still Hsu <[email protected]>
|
Great, once we have added that to the testfiles and tests pass, this is good to be merged! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds a new rule for detecting .NET binaries that are compiled Ahead-of-Time (AoT), as well as another rule for detecting strings related to the TouchSocket library, a Chinese-developed networking library that has been adopted by at least one Chinese APT group.
Related Sample
Additional discussion is required surrounding the example linked in the rule, as both of the rules feature a sample that is a known malicious sample that exceeds 15MB in size and can cause a significant amount of time to process, and may cause timeout for the CI pipeline. I can replace this with a self-written sample Hello World that would meet the requirements for both of these rules and be significantly smaller (~1.6MB) and faster, if other maintainers believe this would be a better approach.