Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
meltedinhex/writing-suricata-and-snort-rulesMalware and ransomware analysis

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-rules

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
RmoOaAe1I+…4m8UMmBA==The CLI checks the SHA-256 and the signature before it writes a file.
Package92197aae…f1409e73
92197aae30a9…6f16f1409e734 files · ⁦3.1 KB⁩
ScanMedium2 findings
  • Executable script shipped with the skillscripts/analyst.py
  • Links to outside domains
See the full scan
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/writing-suricata-and-snort-rules@da7600a

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

bash
python scripts/analyst.py lint rules.rules

Checks 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 unique sid, and a rev.
  • content matches 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:established and matching on unrelated traffic directions.

References

  • See references/api-reference.md for the linter.
  • Suricata and Snort rule docs (linked in frontmatter).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillscripts/analyst.py
  2. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0.0Nov 13, 2026da7600a92197aaeSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login