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/scanning-samples-with-yaraMalware and ransomware analysis

scanning-samples-with-yara

⁨Uses YARA to classify and triage samples at scale: applying rule sets, reading⁩

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/scanning-samples-with-yara

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

SignatureSigned, ed25519
n4bXNoXBtu…OeJtmnBw==The CLI checks the SHA-256 and the signature before it writes a file.
Package794d25cf…35d30a65
794d25cf5bd8…899e35d30a654 files · ⁦3.2 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/scanning-samples-with-yara@da7600a

When to Use

  • You want to classify one or many samples against known malware-family or capability rules.
  • You need to confirm a family hypothesis with a targeted rule and read which strings matched.
  • You are triaging a directory of files and want to flag the suspicious ones.

Do not use a YARA match as proof of family attribution on its own — public rules vary in quality and can over-match. Corroborate with behavior or code analysis.

Prerequisites

  • yara CLI or yara-python (pip install yara-python).
  • A curated rule set (your own plus vetted public rules). Avoid blindly merging large noisy collections.
  • Samples in neutralized form inside the lab.

Workflow

Step 1: Organize rules

Keep rules in categories (family, capability, packer, anomaly) and compile them once for speed. Tag rules so matches are self-describing.

Step 2: Scan and read matches

bash
python scripts/analyst.py scan rules/ sample.bin
# prints matched rule names, tags, and matched strings with offsets

The matched string offsets matter: they tell you where in the file the signal is (header, overlay, resource), which guides deeper analysis.

Step 3: Triage a directory

bash
python scripts/analyst.py scan rules/ ./samples --recursive --summary

Rank files by number/severity of matches to prioritize analyst time.

Step 4: Tune for false positives

If a rule fires on benign files, tighten it: require multiple strings (2 of ($a*)), anchor to file structure (uint16(0) == 0x5A4D), or raise the condition specificity.

Step 5: Promote good signals to detection

A rule that reliably identifies a family or capability becomes a hunting/detection artifact — hand it to the detection-engineering workflow.

Validation

  • Matches reproduce across runs and tools (CLI and yara-python agree).
  • Each kept rule has an acceptable false-positive rate against a known-clean corpus.
  • Match offsets correspond to meaningful file regions, not incidental byte coincidences.

Pitfalls

  • Merging huge public rule packs without curation — noise and false positives explode.
  • Writing rules on packed bytes that change with every build; prefer unpacked or structural features.
  • Over-broad strings (common library text) that match unrelated software.

References

  • See references/api-reference.md for the scanner tool.
  • YARA and yara-python documentation (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, 2026da7600a794d25cfSigned–

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