YARA
v4.6.0 open-sourceThe section your link pointed to isn't on YARA's page any more, so we've brought you to the top.
YARA is a tool that helps malware researchers identify and classify malware samples using rules based on textual or binary patterns.
yara --no-follow-symlinks rules.yar C:\Targets\
yara --disable-console-logs rules.yar target_file
yara --strict-escape rules.yar target_file
yara --skip-larger <threshold> <rules_file> <target_file>
yara --no-follow-links rules.yar /path/to/directory
echo 'rule test { strings: $a = "hello" condition: $a }' | yara - /tmp/sample.bin
yara --fail-on-warnings rules.yar target.bin
yr_compiler_add_fd(compiler, fd, NULL, NULL);
yara --print-module-data rules.yar target.bin
yr_rules_load_stream(rules_fp, &rules);
yara.match('rules.yar', 'target.bin', error_on_warning=True)
Summary
YARA is an open-source pattern-matching tool that helps malware researchers identify and classify malware samples by writing rules combining textual or binary patterns with boolean logic. It runs as a command-line scanner, matching rulesets against a single file or recursively across a directory, and can also be driven from Python scripts via the yara-python extension. It is built for malware analysts and threat researchers who need to fingerprint files by content rather than by hash. The project is multi-platform, running on Windows, Linux, and Mac OS X, and README notes complementary tools like YARA-CI for testing rules and yextend for scanning inside compressed archives. Now in maintenance mode as development shifts to YARA-X, it still sees active upkeep, with 250 contributors and a release cut just 24 days ago.
YARA is a tool that helps malware researchers identify and classify malware samples using rules based on textual or binary patterns.
How YARA helps
Which of my files contain a known-malicious pattern?
scans a file or directory recursively against a ruleset and reports every match by rule name and file path, down to the exact byte offset where the pattern occurred
Did a secret or hardcoded credential leak into my source tree?
matches string and boolean-logic rules against a codebase and names each file that contains the pattern, along with the matched string and its offset
Which files in this batch can I rule out so I only review the real hits?
tags every scanned file with a match count, letting the files that scored zero be filtered out and the remainder narrowed to the ones worth inspecting by hand
What exactly matched, and is it obfuscated or plaintext?
reports the matched string's length and offset and can compute an XOR key against the surrounding bytes, showing whether the content sits in the clear or was disguised
Which malware family does this sample belong to, based on more than its hash?
evaluates the sample's content against rules built from textual or binary patterns and boolean conditions, so a match holds even when the file has been repacked or renamed
Can I classify a sample from inside my own analysis pipeline rather than the command line?
the same ruleset and matching engine is callable from a Python script, returning matches programmatically so classification can run as a step in a larger tool
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for YARA, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail YARA puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Coverage
Missing something? Tell us
What YARA connects to, runs on and detects, read from its release notes and docs. So far: 1 new supported platform.
1 change, tracked since Oct 27, 2026.
-
Oct 272026
new Nine new ELF e_machine architecture constants in the elf module
Expose nine more `e_machine` values in `elf` module (#2248).
Other 1
Nothing first seen in this window. That doesn't mean YARA shipped nothing, only that we found no record of it.
How we count
Read from 1 of 21 release notes and docs updates we hold for YARA. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through YARA's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
21 entries
No entries match these filters.
- October 20261
- October 20251
- May 20241
- February 20241
- March 20231
- April 20221
- March 20221
- April 20211
- April 20201
- October 20191
- August 20181
- November 20171
- May 20171
- September 20161
- June 20151
- February 20151
- November 20141
- August 20143
- March 20141
Project health
Issue, contributor and maintainer activity in VirusTotal/yara, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 12 ±0 vs prior 12 months
- Maintainers 2 +1 joined · −0 left, last 12 months
- Bus factor 2 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close 59 days first maintainer reply 2.5 days
- Open backlog 149 of 1,107 issues ever filed
- Issues opened / month 1 · 0 communitymaintainers
- Open backlog 149
- Contributors / month 1
- Commits / month 2
- Stars 9,868
- bugs 69%
- other 31%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.