writing-suricata-and-snort-rules
Writes and validates Suricata/Snort IDS rules for network-based malware detection,
v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 10 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/writing-suricata-and-snort-rulesWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package92197aae…f1409e73
92197aae30a9…6f16f1409e734 files · 3.1 KBScanMedium2 findings
- Executable script shipped with the skillscripts/analyst.py
- Links to outside domains
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/writing-suricata-and-snort-rules@da7600a
On this page
When to Use
- You need to author IDS rules to detect C2 traffic, malware downloads, or exploit attempts from observed network indicators.
- You want to validate rule syntax and avoid the patterns that cause false positives or silent non-matching.
Do not use broad content matches on common substrings that will flood alerts — anchor with
flow direction, ports, offsets, and uniqueness. This skill builds and lints rules; deploy them
through your IDS change process.
Prerequisites
- The indicators to detect (URI, host header, TLS SNI/JA3, byte pattern) and a target IDS (Suricata or Snort).
Workflow
Step 1: Draft the rule
Choose action, protocol, addresses/ports, direction, and a unique msg, sid, and rev. Add
content/pcre matches anchored with http.uri, tls.sni, flow:established,to_server, and
offsets/depths.
Step 2: Lint the rule
python scripts/analyst.py lint rules.rulesChecks for required fields (msg, sid, rev, classtype), balanced quotes/parentheses,
non-anchored overly short content, and duplicate SIDs.
Step 3: Tune to reduce noise
Add threshold/detection_filter, flowbits, and specific buffers (http.host, dns.query)
to scope matches.
Step 4: Document and stage
Record what each rule detects and stage it for testing against a pcap before production.
Validation
- Every rule has
msg, a uniquesid, and arev. contentmatches are anchored (buffer/offset/flow) rather than free-floating short strings.- Rules parse without unbalanced quotes/parentheses.
Pitfalls
- Free-floating
content:"GET"style matches creating massive false positives. - Duplicate or reused SIDs causing rule-load conflicts.
- Forgetting
flow:establishedand matching on unrelated traffic directions.
References
- See
references/api-reference.mdfor the linter. - Suricata and Snort rule docs (linked in frontmatter).
Files in this version
references/11.1 KB
- api-reference.md1.1 KB
scripts/12.8 KB
- analyst.py2.8 KB
- LICENSE340 B
- SKILL.md2.8 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumFile · Executable script shipped with the skillscripts/analyst.py
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v1.0.0 | Nov 13, 2026 | da7600a | 92197aae | Signed | – |
More from meltedinhex
All from this publisher- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- validating-detections-with-atomic-testsmeltedinhex/validating-detections-with-atomic-tests4
- writing-sigma-detection-rulesmeltedinhex/writing-sigma-detection-rules3
- writing-a-malware-analysis-reportmeltedinhex/writing-a-malware-analysis-report3
More in Malware and ransomware analysis
See the category- yara-sigsdariushoule/yara-sigs4
- monitoring-darkweb-sourcesmukul975/monitoring-darkweb-sources3
- deploying-ransomware-canary-filesmukul975/deploying-ransomware-canary-files3
- implementing-honeypot-for-ransomware-detectionmukul975/implementing-honeypot-for-ransomware-detection3
- yaraaeondave/yara3
- testing-ransomware-recovery-proceduresmukul975/testing-ransomware-recovery-procedures3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login