Back to .md Directory

RE-Bench Formal Scoring Rubric

Defines seven scoring axes, metrics, and a weighted composite formula for evaluating reverse engineering LLMs.

May 2, 2026
0 downloads
3 views
ai llm rag eval
View source

What this file does

Defines seven scoring axes, metrics, and a weighted composite formula for evaluating reverse engineering LLMs.

When to use it

  • Benchmarking LLM performance on malware analysis tasks
  • Designing a reproducible evaluation rubric for security AI
  • Comparing model outputs across CWE detection, ATT&CK mapping, and explanation quality

Assumes this stack

PythonBERTScoreROUGE-L

RE-Bench Formal Scoring Rubric

RE-Bench evaluates reverse engineering LLMs across seven orthogonal axes:

  1. Malware Behavior Understanding
  2. Vulnerability Detection
  3. MITRE ATT&CK Technique Mapping
  4. Capability Extraction
  5. Assembly & Behavior Analysis (LLM Judge)
  6. Explanation Quality
  7. Hallucination Robustness

Each axis is scored independently and combined into a weighted composite.


1️⃣ Malware Behavior Classification

Task Type: Multi-label classification
Datasets: EMBER, MalwareBazaar
Metric: Macro F1

Score RangeInterpretation
0.90–1.00Near-human malware family understanding
0.75–0.89Strong detection, minor confusion
0.60–0.74Moderate understanding
< 0.60Weak malware comprehension

Macro F1 is used to avoid majority-class bias.


2️⃣ Vulnerability Detection (CWE-Level)

Task Type: Multi-class or multi-label CWE prediction
Datasets: Big-Vul, Juliet
Metrics:

  • Macro F1 (primary)
  • Precision / Recall
  • Per-CWE F1 (secondary)

Auto-CWE F1 Formula

For each CWE:

F1 = 2 × (Precision × Recall) / (Precision + Recall)

Macro-F1 across all CWEs is reported as primary score.


3️⃣ MITRE ATT&CK Technique Mapping

Task Type: Single-label classification
Datasets: BIG-15, MELD
Metric: Accuracy (with normalization)

Predictions are normalized before comparison:

  • Synonyms resolved (e.g. "process injection" → T1055)
  • Sub-techniques collapsed to base technique (e.g. T1055.001 → T1055)
Score RangeInterpretation
0.85–1.00Strong ATT&CK knowledge
0.65–0.84Moderate technique recognition
< 0.65Weak technique mapping

4️⃣ Capability Extraction

Task Type: Multi-label extraction
Datasets: MELD, Malrec
Metric: Macro F1 (token-level, after capability normalization)

Capability synonyms are normalized before scoring (e.g. "dll injection" → "process injection").

Score RangeInterpretation
0.80–1.00Accurate capability identification
0.60–0.79Partial capability coverage
< 0.60Significant capability gaps

5️⃣ Assembly & Behavior Analysis (LLM Judge)

Task Type: Free-text generation
Datasets: BIG-15 (assembly understanding), MELD / Malrec (behavior explanation)
Metric: Rubric score 0–3, normalized to [0, 1]

Rubric

ScoreCriteria
3Correct technique/behavior identified with accurate supporting detail
2Correct identification, minor inaccuracies in detail
1Partially correct — relevant but incomplete or imprecise
0Incorrect, irrelevant, or no response

Normalized Score

$$\text{Judge Score} = \frac{\text{raw rubric score}}{3}$$

A heuristic keyword-overlap fallback is used when an LLM judge is unavailable (≥0.75 overlap → 3, ≥0.50 → 2, ≥0.25 → 1, else 0).


6️⃣ Explanation Quality

Task Type: Free-text explanation generation
Metrics:

  • ROUGE-L
  • BERTScore F1
ScoreInterpretation
> 0.85 BERTScoreHigh semantic alignment
0.70–0.85Reasonable explanation
< 0.70Low semantic similarity

Human spot-check validation is recommended for publication.


7️⃣ Hallucination Robustness

Measured using:

  • Unsupported claim rate
  • Binary contradiction rate
  • Out-of-scope CWE hallucination frequency

Hallucination Score

Hallucination Score = 1 − (False Claims / Total Claims)


🏆 Composite Score

Default weights:

MetricWeightDatasets
Malware F10.20EMBER, MalwareBazaar
CWE F10.20Big-Vul, Juliet
MITRE Mapping Accuracy0.15BIG-15, MELD
Capability Extraction F10.15MELD, Malrec
Assembly / Behavior Judge0.15BIG-15, MELD, Malrec
Explanation Similarity0.10All
Hallucination Robustness0.05All

Composite = Weighted Sum

Weights may be adjusted but must be reported.

What's inside

7 scoring axes, each with task type, dataset, metric, and score ranges, plus a composite weight table.

Change this for your project

  • Replace dataset names like EMBER, MalwareBazaar, Big-Vul, Juliet, BIG-15, MELD, Malrec with your own
  • Adjust default weights in the composite score table (e.g., 0.20 for Malware F1) to match your priorities
  • Modify score range thresholds (e.g., 0.90, 1.00) to fit your evaluation scale

Where it goes

Keep it in your repository where the agent or team that needs it will read it.

Worth borrowing

  • Normalizing synonyms and collapsing sub-techniques before scoring to avoid penalizing valid alternative labels
  • Using a heuristic keyword-overlap fallback when an LLM judge is unavailable
  • Reporting a hallucination score as 1 minus the false claim rate

Related Documents