Ingo Money
bd_d5319e025594e952 · schema v1 · pii pii-v1
Full breach record for Ingo Money →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group INC Ransom 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.
Source: Ransomware.live
Post text · scraped from the leak site
On a Mission to Make Money Movement Instant, Digital and Secure Since 2001, we have focused on a singular mission: to give people and businesses instant, digital and secure access to their money...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Nov 23, 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
Linked disclosures
Why this link?Regulatory filings (6) · sorted by filing gap
- Indiana State AGbd_07deaf206dcd878a2024-06-26 · +216dCandidate
- Massachusetts State AGbd_591665c46a2cdd4d2024-06-29 · +219dVerified
- Washington State AGbd_d33dcc1e99dcc9cb2024-07-02 · +222dVerified
- Massachusetts State AGbd_5fad210b837d2a462024-07-08 · +228dVerified
Show 2 more filings ↓Show fewer ↑up to 258d gap
- Maine State AGbd_10f7c83fa3539c482024-08-05 · +256dVerified
- California State AGbd_9aca85417932278e2024-08-07 · +258dVerified
Filing propagation · 7 filings · 5 states
View merged incident ↗Pattern: first filing Nov 23, last Aug 7 (CA) — a 258-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
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.