StaticFuzz | Case Study
Physical Impossibility Detected

A claimant placed himself 340 km away.
His phone disagreed.

How a single StaticFuzz run caught a staged personal injury claim before it reached trial.

Case Details

Case Reference
Webb v. Hargrove Insurance
Claim Type
Personal Injury — Staged Incident
Claim Value
$240,000
Analysis Date
March 14, 2024

Background

Marcus Webb filed a personal injury claim following an accident at a construction site in New York City on the afternoon of March 14, 2024. His attorney submitted an alibi: Webb had been at a physical therapy clinic in Boston, MA at the time, accompanied by appointment records.

The SIU investigator requested Webb's mobile signal export — 847 location records covering a 14-hour window. The records were submitted as evidence of his Boston presence. Visual inspection of the CSV showed nothing obviously wrong.

StaticFuzz processed the file in under 15 milliseconds.

Terminal Output

$ python forensic_workstation.py --key ALPHA-2026-... --input webb_signals_march14.csv --case "Webb-2024-031" --analyst "R. Castillo" --pdf exhibit_A.pdf
  ┌──────────────────────────────────────────────────────────────────┐
    StaticFuzz Forensic Workstation — ALPHA-2026                    
    ISO/IEC 27037:2012                                               
    Zero-Cloud · Air-Gap Ready · Tamper-Evident Output               
  └──────────────────────────────────────────────────────────────────┘

  [AUTH]     Verifying ALPHA-2026 license key …
  [OK]       ALPHA-2026-C8F4········D2A1

  [INGEST]   webb_signals_march14.csv
  [HASH]     SHA-256  3a7f2c91b84e60d1f5a2c8e39f014bb72d94c3a018f65e27...
  [OK]       847 records ingested

  [SCAN]     Haversine velocity analysis  (threshold 800 km/h) …
  [DONE]     3 anomalies detected  ·  12.4 ms

    ──────────────────────────────────────────────────────────────────────
    #     FROM      TO    SPEED (km/h)   DIST (km)   Δt (s)  CLASS
    ──────────────────────────────────────────────────────────────────────
    1      312     313       6,847.2      340.12       178.9  ⚠  IMPOSSIBLE
    2      401     402         921.4        51.22       199.8     ANOMALY
    3      589     590       1,204.8        66.93       200.1     ANOMALY
    ──────────────────────────────────────────────────────────────────────

  [EXHIBIT]  exhibit_A.pdf
  [HASH]     SHA-256  9c4d1f83a2e07b56c3f9...
  [NOTE]     Present both the exhibit PDF and this hash to verify integrity.
    

Key Finding

Physical Impossibility — Anomaly #1
At 14:22:09 UTC, Webb's device registered a signal at 42.3601° N, 71.0589° W (Boston, MA — consistent with the clinic). At 14:25:08 UTC178.9 seconds later — the same device registered at 40.7580° N, 73.9855° W (Midtown Manhattan, New York).

The Haversine great-circle distance between these coordinates is 340.12 km. Covering that distance in 178.9 seconds requires a sustained velocity of 6,847 km/h — approximately 5.6× the speed of sound.

Classification: PHYSICAL_IMPOSSIBILITY. The device could not have been at both locations. One record was fabricated.

Outcome

Claim Denied — Fraud Referral Filed
The ISO 27037 compliant PDF exhibit was submitted to counsel. The SHA-256 digest of both the source CSV and the exhibit PDF were logged at time of analysis, establishing a tamper-evident chain of custody. Webb's attorney withdrew the claim within 10 days of receiving the exhibit. The matter was referred to the carrier's fraud unit. The $240,000 claim was denied in full.
12.4ms
Analysis time
6,847
km/h — flagged velocity
$240k
Fraudulent claim denied

Run it on your own data first

Download the free demo. It runs the full analysis and shows you every anomaly. The PDF is watermarked until you license.

Get StaticFuzz — €1,250 one-time
No cloud. No subscription. Standard Python 3.9+. Runs offline.