DisclosureLens
GLOBALMalwareRansomwareLockbit5Ransom DemandedActor NamedData Leak ThreatenedData PublishedOFAC SanctionedCritical

没有找到站点

bd_ddd8cd0b33012c8c · schema v1 · pii pii-v2

Severity

Critical

Discovered

—

Filed

Oct 23, 2026

To disclose

—

Affected

Not disclosed

Confidence

50%
Full breach record for 没有找到站点 →

Threat-actor claim — not a regulatory filing

This row is a claim by the ransomware group Lockbit5 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.

Sanctions caution: Lockbit5 carries US sanctions exposure — OFAC has designated the group or its operators. Public reporting is permitted (informational-materials exemption, 50 U.S.C. § 1702(b)(3)) — but any payment or material support may violate sanctions. Consult counsel before engaging.

Group activity: Not FoundDiscovered: 2026-10-23

Source: Ransomware.live

Post text · scraped from the leak site

Lido boutique hotel, with 100 rooms, shops, restaurants and gym, creates a comfortable and intimate...

Incident timeline — mostly unverified

? — ?

Breach window unknown

Oct 23, 2026

Claim posted

—

No filing yet · watching

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

Claim → filing

—

Compliance clock

Not assessable

Tracked as a single-filing incident — the only disclosure on record for this event so far.Unverified claimView incident

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.

No regulatory filing corroborates this yet — it is the attacker's own assertion. Watch this entity to be notified the moment a filing corroborates or contradicts it.

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 2024-08-17

lockbit5

According to ransomware.live, LockBit 5.0 ("ChuongDong") emerged in September 2025 as the group's resurgence following the February 2024 law enforcement takedown, introducing cross-platform payloads targeting Windows, Linux, and VMware ESXi with enhanced evasion capabilities and continuing the RaaS affiliate model of its predecessors.

656 tracked hereFull profile →