Neo23x0/signature-base

YARA signature and IOC database for my scanners and tools

View on GitHub ↗Jump to charts ↓

Neo23x0/signature-base has 3k+ stars and 650+ forks on GitHub, is written in YARA, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 46 minutes ago
Added to GitGenius on September 22nd, 2026
Created on February 15th, 2016
Open Issues & Pull Requests: 20 (+0)
GitHub issues: Enabled
Number of forks: 677
Total Stargazers: 3,049 (+0)
Total Subscribers: 195 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 18.5 days
Mean response time: 245.2 days
90th percentile: 947.8 days
Tracked items: 9

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 673 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Signature-Base is a YARA signature and IOC database designed for threat detection and incident response.

The project addresses the need for high-quality detection rules and indicators of compromise in security scanning workflows. It maintains a curated collection of YARA rules and IOC files organized into clear directory structures: IOCs stored as simple CSV files, YARA rules in a dedicated directory, threat intelligence integrations for MISP and OTX feeds, and miscellaneous supporting files. The approach prioritizes minimal false positives, consistent rule formatting, and structural clarity to make the signatures practical for real-world use.

The tool is built primarily for integration with LOKI and THOR Lite scanners, though the YARA rules can be adapted for use in other tools. Developers should be aware that some rules use external variables specific to those scanners; rules relying on undefined identifiers are documented in a separate file and should be removed if using the signatures elsewhere. The project accepts community contributions through pull requests for both bug fixes and new rules, with false positive reports handled through the issue tracker. A commercial rule set with significantly expanded coverage is available separately for organizations requiring more comprehensive detection capabilities.

The project maintains an active approach to community feedback, with documented processes for reporting issues and contributing improvements. Pull requests are accepted for rule additions and corrections, and the maintainers engage with the community through documented contribution guidelines.