Skip to main content

Ransomware victim disclosure

All victims

Factory Five Racing Inc

listed as FactoryFive · Claimed by Metaencryptor · listed 17 hours ago

Today
Age
since listed · data leaked

Status timeline

  1. ListedAug 23, 2026
  2. Data leakeddate unknown

At a glance

Status
Data leaked
Listed on leak site
Aug 23, 2026

About the victim

AI dossier — public-source company profile

Factory Five Racing Inc manufactures high-performance kit cars (Cobra replicas, Mk5/Mk4 Roadsters, Type 65 Coupe, '33 Hot Rod, and XTF models) based in Wareham, Massachusetts. The company operates with approximately 90 employees and generates annual revenue of $5.5–6.5 million, with significant credit card processing volume (~$4.3M/yr).

Industry
Specialty Automotive Manufacturing & Kit Cars
Address
9 Tow Road, Wareham, MA 02571-1086
Employees
90

Attack summary

Severity: critical — Confirmed exfiltration of sensitive regulated data including PII at scale (CRM contacts), financial/banking records, tax documentation, insurance data, active litigation files with witness testimony, and PCI DSS-regulated payment processing information. Multiple regulatory frameworks implicated: PCI DSS ($4.3M processing), MA 201 CMR 17.00, GDPR, CCPA. Company undergoing active IRS and MA Sales Tax audits. Litigation exposure and reputational damage from case file disclosure.

metaencryptor claims to have exfiltrated approximately 130 GB of data from Factory Five Racing, including correspondence, CRM records, ERP/pricing systems, CAD engineering files, banking statements, insurance policies, tax documentation, legal contracts, NDAs, and database backups. The group has published pricing configurator scripts and onboarding documents as proof.

critical

Data the group says was taken

AI dossier — extracted from the leak post
  • email archives (PST)
  • CRM contact data (GoldMine)
  • ERP and pricing systems
  • engineering CAD files (SolidWorks, Rhino)
  • banking statements
  • insurance policies
  • tax documentation
  • legal contracts and NDAs
  • litigation case files and correspondence
  • database backups

The group's post references roughly 7 proof files.

What the group claims

Factory Five Racing Inc — kit-car manufacturer (Cobra replicas, GTM, Type 65 Coupe, 33 Hot Rod). 9 Tow Road, Wareham MA 02571-1086. ~90 employees, 158 endpoints. Revenue $5.5-6.5M/yr (credit card processing ~$4.3M, avg ticket $1245). Exfiltrated data categories (~130GB): correspondence (PST archives), CRM contacts (GoldMine), ERP/pricing, engineering CAD (SolidWorks/Rhino), banking statements, insurance policies, tax documentation, legal contracts/NDAs, database backups. Includes detailed materials on several ongoing lawsuits — parties, witnesses, testimonies, and related case files, alongside private correspondence. Risk zones: PCI DSS (card processing $4.3M/yr), MA 201 CMR 17.00 (Massachusetts personal data protection), GDPR (EU clients), CCPA (California clients), active IRS audit, active MA Sales Tax audit, FTC Safeguards Rule. Reputational: customer warranties, partner contracts (SEMA supplier), licenses, litigation exposure. CEO: David T. Smith.

The leak post

captured from the group's site
Factory Five Racing Inc — kit-car manufacturer (Cobra replicas, GTM, Type 65 Coupe, 33 Hot Rod). 9 Tow Road, Wareham MA 02571-1086. ~90 employees, 158 endpoints. Revenue $5.5-6.5M/yr (credit card processing ~$4.3M, avg ticket $1245). Exfiltrated data categories (~130GB): correspondence (PST archives), CRM contacts (GoldMine), ERP/pricing, engineering CAD (SolidWorks/Rhino), banking statements, insurance policies, tax documentation, legal contracts/NDAs, database backups. Includes detailed materials on several ongoing lawsuits — parties, witnesses, testimonies, and related case files, alongside private correspondence. Risk zones: PCI DSS (card processing $4.3M/yr), MA 201 CMR 17.00 (Massachusetts personal data protection), GDPR (EU clients), CCPA (California clients), active IRS audit, active MA Sales Tax audit, FTC Safeguards Rule. Reputational: customer warranties, partner contracts (SEMA supplier), licenses, litigation exposure. CEO: David T. Smith.  
|  [CONFIGURATOR PRICING SCRIPT - FFR - SRV2.xlsx](https://metacrpttdfpbm4qoxzcrqqgr6e6zafpazgxm72knmujw2mwvi34rwad.onion/0AFC:675a977f4d6b460ed9ccbbcb4d75117ae02209187bb0af2d7b01f0fab79e1ce4/0AFC:97deec99241a33e261d126ec80cd3137c5a…

Sources

Source

Indexed 17 hours ago

This page surfaces a public ransomware disclosure indexed by Darkfield. Original posts come from the operator's own leak site; we cross-check against ransomware.live, RansomLook and RansomWatch where applicable. Share this URL freely.

Is this your supplier? Your competitor? You?

Pro plans monitor your domain, corporate emails, and crypto wallets across every new ransomware leak-site post, breach dump and Telegram callout — alerts within 5 minutes.

Disclosure context

About Metaencryptor

Metaencryptor is a relatively new ransomware group that emerged in August 2023, operating with primarily financial motivations and targeting organizations across multiple sectors and geographical regions. The group appears to be an independent operation rather than a Ransomware-as-a-Service model, though limited public documentation makes definitive attribution challenging regarding their specific country of origin or connections to established cybercriminal networks. Based on their targeting patterns, Metaencryptor demonstrates a preference for manufacturing organizations, business services, and transportation/logistics companies, with their operations concentrated primarily in Western nations including Germany, the United States, Canada, Spain, and the United Kingdom. With 31 documented victims since their emergence, the group represents a moderate but persistent threat in the ransomware landscape. However, due to their recent emergence and relatively lower profile compared to major ransomware families, comprehensive technical analysis of their attack methodologies, encryption techniques, and specific initial access vectors has not been extensively documented by major cybersecurity firms or government agencies. The group's current operational status remains active as of available intelligence, though the limited public reporting suggests they operate with a smaller scale and lower visibility than prominent ransomware-as-a-service operations that typically attract more attention from law enforcement and security researchers. The group has been linked to 38 public disclosures across our corpus. First observed on a leak site on August 16, 2023; most recent post August 23, 2026. The operation is currently inactive.

Timeline of this disclosure

  • August 23, 2026FactoryFive listed by Metaencryptoron the group's public leak site

Sector and geography

This disclosure adds to ransomware activity in the Manufacturing sector, which has 3,692 disclosures indexed across all operators we track. Geographically, FactoryFive is reported in United States, a country with 3,164 ransomware disclosures in our corpus.

If your organisation is affected

A listing by Metaencryptor means FactoryFive appeared on a ransomware extortion site and data attributed to it has been published. If this is your organisation, or a supplier you depend on, the priority is to confirm the intrusion and contain it before the window to act closes.

  • Engage your incident-response team and preserve forensic evidence before remediating — do not wipe affected systems first.
  • Force a password reset and revoke active sessions for exposed accounts; rotate any credentials, API keys or certificates that may have been in the stolen data.
  • Assess regulatory notification duties (GDPR, NIS2, sector regulators) — many carry a 72-hour reporting clock from awareness.
  • Report the incident to your national CERT, CISA (United States), as required for your jurisdiction.
  • Monitor for the data appearing on Metaencryptor's leak site and across paste and breach channels, and brief downstream partners who may be exposed through you.

How we know this. Darkfield monitors public ransomware leak sites continuously, archiving every new disclosure and the data later released against the victim. Each entry on this page is sourced from the operator's own publication and cross-checked against complementary OSINT feeds (RansomLook, ransomware.live, RansomWatch). We do not collect or host stolen data — only the metadata, timestamps and screenshots needed to make the public disclosure searchable and accountable. Records here are corrected when the original post is edited, retracted, or merged with another disclosure.