Skip to main content
Data products

YARA rules with their provenance

Third-party YARA rules from public repositories, compiled with yara-x and deduplicated across sources. Each rule keeps its source, upstream commit and declared licence, and its author when one is named.

No YARA rules have been collected yet: there is nothing to download or to try.

format
YARA · STIX 2.1
delivery
zip · TAXII 2.1 · yara-rules
built
—
GET/rules/summary

No rules have been collected yet.

—
Capabilities

Key features at a glance.

Provenance on every rule

Source, upstream path, commit or release, author, and the licence the rule or its repository declares.

Compiled before it is served

Each rule compiles on its own with yara-x, and each source file compiles whole before the zip is published. A rule that fails is left out.

One zip

One .yar file per source, with manifest.json, NOTICE.md and the licence texts. Its ETag changes with its content only: If-None-Match answers 304.

TAXII 2.1 collection

yara-rules: one STIX 2.1 indicator per rule, pattern_type yara, read incrementally with added_after.

Versions

A rule changed upstream keeps its STIX id and gets a new version. A rule found in several sources is served once.

Withdrawals

A rule removed upstream is revoked over TAXII and leaves the next zip.

Applications

Use cases to evaluate first.

  1. File and memory scans

    Load each .yar file as a namespace of its own in YARA-X or yara-python.

  2. Threat hunting

    Find rules by source, author or name in the zip's manifest.json, or through the rules API.

  3. OpenCTI

    Import the collection with the TAXII connector, with the decay exclusion described below.

  4. Your own pipeline

    Plain HTTPS and an API key: fetch the zip again when its ETag changes.

Specification

What you receive. Check it before you connect a tool.

Format
The zip: one .yar file per source, each rule with the private rules it depends on, plus manifest.json, NOTICE.md and the licence texts. Over TAXII: one STIX 2.1 indicator per rule, pattern_type yara.
TAXII collection
yara-rules, listed beside the IOC collections: a client that polls every collection imports the rules too.
Access
Pro and Enterprise, or a feed trial, with your API key. Downloads and polling do not use the monthly request quota.
Checks
Each rule compiles on its own with yara-x, then each file compiles whole. A rule that fails is left out; manifest.json lists what the zip skipped and why.
Refresh
Every source is checked every 6 hours; a new zip is built only when a rule changes.
Versions
A changed rule keeps its STIX id; a withdrawn one comes back with revoked: true.

Before you use them

Licences, OpenCTI and MISP.

Licences

The rules are third-party works under the licences their authors declared, non-commercial and copyleft ones included. Each keeps its licence, and the zip carries NOTICE.md and the licence texts. isMalicious grants no rights beyond those licences.

OpenCTI decay

Add a decay exclusion rule on the label detection-rule, or OpenCTI's decay revokes the rules on its own schedule. A rule ends when its source withdraws it.

MISP

Convert the collection with misp-stix: an indicator with pattern_type yara becomes a MISP yara object.

Newest rules

The rules added most recently. Metadata only: the rules themselves are in the zip and the collection.

No rules have been collected yet, so none is listed.

FAQ

Frequently asked questions.

How many YARA rules are there?

None yet: no YARA rules have been collected.

Where do the rules come from?

From public repositories and feeds published by third parties. Every rule carries its source, its licence and, when one is named, its author, inside the zip and over TAXII. A rule found in several sources is served once, from the source ranked higher.

Can I use the rules in a commercial product?

It depends on each rule's licence. The rules are third-party works under the licences their authors declared, some of them non-commercial or copyleft. isMalicious grants no rights beyond those licences: check a rule's licence before you redistribute it or build it into a product.

How often are the rules updated?

Every source is checked every 6 hours. A new zip is built only when a rule is added, changed or withdrawn, so a download with If-None-Match answers 304 until then.

Will the rules load in libyara?

Each file compiles whole with yara-x when the zip is built, and the rules libyara refused when last checked are left out. README.md in the zip names the engines. If a file fails in yours, write to us with the engine and its version.

Test it with your own indicators.

The YARA rules will come with Pro, Enterprise and the feed trial once the collection holds rules. Until then, read how the zip and the collection are served, or tell us what you need.

Pro €99/month · Enterprise on quote · not in Free or Basic · downloads and polling do not use your request quota