DisclosureLens
GLOBALMalwareProfessional ServicesProfessional ServicesRansomwareLockBit 3.xRansom DemandedActor NamedData Leak ThreatenedData PublishedOFAC SanctionedCritical

Infosys BPM

bd_b8910ec32724a786 · schema v1 · pii pii-v1

Severity

Critical

Discovered

—

Filed

Nov 4, 2023

To disclose

—

Affected

Not disclosed

Linked

3 filings

Confidence

50%
Full breach record for Infosys BPM →

Threat-actor claim — not a regulatory filing

This row is a claim by the ransomware group LockBit 3.x 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: LockBit 3.x 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: Business ServicesDiscovered: 2023-11-04
View aggregator listing on ransomware.liveView merged incident timeline

Source: Ransomware.live

Post text · scraped from the leak site

https://www.reuters.com/technology/indias-infosys-says-us-unit-hit-by-cyber-security-event-2023-11-03/U.S. unit, Infosys McCamish Systems, a 12 billion business process management corporation with HQ in India.2000+ systems were encrypted. We...

Incident timeline — mostly unverified

? — ?

Breach window unknown

Nov 4, 2023

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 3 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (2) · sorted by filing gap

Filing propagation · 3 filings · 2 states

View merged incident ↗
Leak SiteNov 4 · first · this page
New Hampshire State AG+236d
South Carolina State AG+236d

Pattern: first filing Nov 4, last Jun 27 (SC) — a 236-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.