YARA 3.11 releases, The pattern matching swiss knife
YARA is a tool aimed at (but not limited to) helping malware researchers to identify and classify malware samples. With YARA you can create descriptions of malware families (or whatever you want to describe) based on textual or binary patterns. Each description, a.k.a rule, consists of a set of strings and a boolean expression that determine its logic. Let’s see an example:
The above rule is telling YARA that any file containing one of the three strings must be reported as silent_banker. This is just a simple example, more complex and powerful rules can be created by using wild-cards, case-insensitive strings, regular expressions, special operators and many other features that you’ll find explained in YARA’s documentation.
It is multi-platform, running on Windows, Linux, and Mac OS X, and can be used through its command-line interface or from your own Python scripts with the Yara-python extension.
If you plan to use YARA to scan compressed files (.zip, .tar, etc) you should take a look at yextend, a very helpful extension to YARA developed and open-sourced by Bayshore Networks.
YARA 3.11 releases.
- More flexible “xor” modifier.
- Implement “private” strings (#1096)
- Add “field_offsets” to “dotnet” module.
- Implement “crc32” functions in “hash” module.
- Improvements to “rich_signature” functions in “pe” module.
- Implement sandboxed API using SAPI
- BUGFIX: Some regexp character classes not matching correctly when used with “nocase” modifier (#1117)
- BUGFIX: Reduce the number of ERROR_TOO_MANY_RE_FIBERS errors for certain hex pattern containing large jumps (#1107)
- BUGFIX: Buffer overrun in “dotnet” module (#1108)
- BUGFIX: Segfault in certain Windows versions (#1068)
- BUGFIX: Memory leak while attaching to a process fails (#1070)
Copyright (c) 2007-2016. The YARA Authors. All Rights Reserved.
Christian Blichmann <firstname.lastname@example.org>
Hilko Bengen <email@example.com>
Joachim Metz <firstname.lastname@example.org>
Karl Hiramoto <email@example.com>
Mike Wiacek <firstname.lastname@example.org>
Shane Huntley <email@example.com>
Stefan Buehlmann <firstname.lastname@example.org>
Victor M. Alvarez <email@example.com>;<firstname.lastname@example.org>
Wesley Shields <email@example.com>