Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rule specs #13

Open
8 tasks
KosmX opened this issue Jun 13, 2023 · 1 comment · May be fixed by #14
Open
8 tasks

Rule specs #13

KosmX opened this issue Jun 13, 2023 · 1 comment · May be fixed by #14
Labels
documentation Improvements or additions to documentation

Comments

@KosmX
Copy link
Owner

KosmX commented Jun 13, 2023

Matching rules

Standard way for representing JVM malware signatures.
Rules should be similar to Yara rules (just for JVM application) This means

  • Binary sequence matches (mostly for asset matching)
  • Filtered Java ASM instruction sequences (for example only check for method invocations, but all of them)
    Ability to match only in selected functions could be useful
  • Optionally limit file/asm sequence matches to files/classes/functions (Updater.class/* or */<clinit>)
  • filename matches (with regex)
  • function name/id matches
  • Match conditions like "at least 10" or "$a or $b and $c" (multiple match conditions has to be allowed)
  • per-malware threat level and lookup ID. Lookup ID should direct users to a website dedicated to malware details and removal guide.
  • per-rule match id allowing us to see exact matching details.
@KosmX
Copy link
Owner Author

KosmX commented Jun 13, 2023

1 malware can have multiple rules, 1 rule can have multiple matches and conditions

@KosmX KosmX added the documentation Improvements or additions to documentation label Jun 13, 2023
@KosmX KosmX linked a pull request Jun 13, 2023 that will close this issue
25 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant