DisclosureLens
GLOBALMalwareGovernmentGovernmentRansomwareBlackSuitRansom DemandedActor NamedMedium

Gloucester County Virginia

bd_1882e6fc2ec7a369 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Filed

May 15, 2025

To disclose

Affected

Not disclosed

Linked

4 filings

Confidence

50%
Full breach record for Gloucester County Virginia

Threat-actor claim — not a regulatory filing

This row is a claim by the ransomware group BlackSuit (formerly Royal) on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.

Group activity: Public SectorDiscovered: 2025-05-15

Source: Ransomware.live

Post text · scraped from the leak site

The Committee is comprised of residents of Gloucester County who are appointed by the Gloucester County Board of Supervisors to serve for a term of 2 years. Meetings are held the third Wednesday of each month in the first floor conference room of County Building One, 6467 Main Street. (The Committee generally does not meet in July and the December meeting is to be announced.) Meetings start at 6:30 PM and are open to the public. Those interested in Committee activities are encourage to attend. Prior to attending, please call the Clean Community Office to verify the location and time of the meeting. Proceedings of the Committee are governed by its Bylaws. The program is administered by a Clean Community Coordinator and supported by hundreds of Gloucester residents and businesses who give generously of their time to help keep the County of Gloucester beautiful, clean, and litter free.

Incident timeline — mostly unverified

? — ?

Breach window unknown

May 15, 2025

Claim posted

Corroborated · see linked filings

Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.

Claim → filing

Compliance clock

Not assessable

This filing is one of 4 about the same incident.View merged incident

Linked disclosures

Why this link?

Ransomware claims (1)

Regulatory filings (2) · sorted by filing gap

Filing propagation · 3 filings · 2 states

View merged incident ↗
Leak SiteMay 15 · first · this page

Pattern: first filing May 15, last Jul 2 (ME) — a 48-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claimThis record

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source ceiling

  • actor name
  • victim claim
  • ransom/leak status
  • discovery date
  • materiality
  • notification
  • affected count
  • confirmed data types
  • compliance clock

The ✕ fields stay blank until a regulatory filing or victim disclosure lands.

About this groupFirst seen 2023-06-12

blacksuit

According to ransomware.live, According to Trend Micro, this ransomware has significant code overlap with Royal Ransomware.

430 tracked hereFull profile →