TFTHREATFADE
ProductDetectionHow it worksIntegrationsResearchSecurityDocsPlaygroundPricingEnterprise
GitHub
ProductDetectionHow it worksIntegrationsResearchSecurityDocsPlaygroundPricingEnterprise
HomeDetection science

Entropy and statistical deviation in the detection pipeline

How rolling Shannon entropy and statistical deviation participate in ThreatFade's evidence-first pipeline.

ThreatFade EngineeringPublished 2026-08-237 minEvidence: Project validation
validated

Signal extraction

ThreatFade documents a hybrid encrypted/unencrypted signal extraction path followed by rolling Shannon entropy and statistical deviation. These features are used as evidence inputs to the detection pipeline.

validated

Why entropy is not a verdict

Entropy describes a property of an observed signal. A change in entropy can be meaningful, but the same numerical change can arise from many benign causes. ThreatFade therefore combines statistical deviation with detection rules and evidence rather than presenting entropy as a standalone malware classifier.

observed signal
      │
      ▼
feature extraction
      │
      ├── rolling entropy
      └── statistical deviation
              │
              ▼
        detection rules
              │
              ▼
      confidence + evidence
synthetic

The diagram above is a conceptual representation of the documented pipeline. It is not a benchmark result.

Evaluation boundary

The repository includes deterministic benchmarking and robustness tests. Those tests are useful for regression and engineering validation, but they should not be confused with independent measurement on a representative labeled corpus.

planned

References

  1. ThreatFade engine repository README — detection capabilities and pipeline.

References

  1. ThreatFade engine README
On this page
  1. Research question
  2. Detection model
  3. Evidence boundary
THREATFADE / TINLANCE LIMITEDSource on GitHub